linux-kernel - Re: [PATCH v4 02/11] memcg: document cgroup dirty memory interfaces

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 29 Oct 2010 14:37:30 -0700
From:	Greg Thelen <gthelen@...gle.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	containers@...ts.osdl.org, Andrea Righi <arighi@...eler.com>,
	Balbir Singh <balbir@...ux.vnet.ibm.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Daisuke Nishimura <nishimura@....nes.nec.co.jp>,
	Minchan Kim <minchan.kim@...il.com>,
	Ciju Rajan K <ciju@...ux.vnet.ibm.com>,
	David Rientjes <rientjes@...gle.com>,
	Wu Fengguang <fengguang.wu@...el.com>
Subject: Re: [PATCH v4 02/11] memcg: document cgroup dirty memory interfaces

Andrew Morton <akpm@...ux-foundation.org> writes:

> On Fri, 29 Oct 2010 00:09:05 -0700
> Greg Thelen <gthelen@...gle.com> wrote:
>
>> Document cgroup dirty memory interfaces and statistics.
>> 
>>
>> ...
>>
>> +When use_hierarchy=0, each cgroup has dirty memory usage and limits.
>> +System-wide dirty limits are also consulted.  Dirty memory consumption is
>> +checked against both system-wide and per-cgroup dirty limits.
>> +
>> +The current implementation does enforce per-cgroup dirty limits when
>
> "does not", I trust.

Correct.  Thanks.

>> +use_hierarchy=1.  System-wide dirty limits are used for processes in such
>> +cgroups.  Attempts to read memory.dirty_* files return the system-wide values.
>> +Writes to the memory.dirty_* files return error.  An enhanced implementation is
>> +needed to check the chain of parents to ensure that no dirty limit is exceeded.
>> +
>>  6. Hierarchy support
>>  
>>  The memory controller supports a deep hierarchy and hierarchical accounting.
>> -- 
>> 1.7.3.1
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@...ck.org.  For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@...ck.org"> email@...ck.org </a>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/