Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> writes: > On Fri, 29 Oct 2010 00:09:05 -0700 > Greg Thelen <gthelen@xxxxxxxxxx> 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@xxxxxxxxxx For more info on Linux MM, > see: http://www.linux-mm.org/ . > Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a> -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>