[PATCH v4 02/11] memcg: document cgroup dirty memory interfaces
gthelen at google.com
Fri Oct 29 14:37:30 PDT 2010
Andrew Morton <akpm at linux-foundation.org> writes:
> On Fri, 29 Oct 2010 00:09:05 -0700
> Greg Thelen <gthelen at google.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.
>> +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.
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo at kvack.org. For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont at kvack.org"> email at kvack.org </a>
More information about the Containers