On Mon, Apr 28, 2014 at 02:26:45PM +0200, Michal Hocko wrote: > Describe low_limit_in_bytes and its effect. > > Signed-off-by: Michal Hocko <[email protected]> > --- > Documentation/cgroups/memory.txt | 9 +++++++++ > 1 file changed, 9 insertions(+) > > diff --git a/Documentation/cgroups/memory.txt > b/Documentation/cgroups/memory.txt > index add1be001416..a52913fe96fb 100644 > --- a/Documentation/cgroups/memory.txt > +++ b/Documentation/cgroups/memory.txt > @@ -57,6 +57,7 @@ Brief summary of control files. > memory.memsw.usage_in_bytes # show current res_counter usage for > memory+Swap > (See 5.5 for details) > memory.limit_in_bytes # set/show limit of memory usage > + memory.low_limit_in_bytes # set/show low limit for memory reclaim > memory.memsw.limit_in_bytes # set/show limit of memory+Swap usage > memory.failcnt # show the number of memory usage hits > limits > memory.memsw.failcnt # show the number of memory+Swap hits > limits > @@ -249,6 +250,14 @@ is the objective of the reclaim. The global reclaim aims > at balancing > zones' watermarks while the limit reclaim frees some memory to allow new > charges. > > +Groups might be also protected from both global and limit reclaim by > +low_limit_in_bytes knob. If the limit is non-zero the reclaim logic > +doesn't include groups (and their subgroups - see 6. Hierarchy support) > +which are bellow the low limit if there is other eligible cgroup in the
'below' :-) Although I really like that spello. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
