On Tue, Sep 18, 2012 at 06:03:58PM +0400, Glauber Costa wrote: > From: Suleiman Souhlal <[email protected]> > > We currently have a percpu stock cache scheme that charges one page at a > time from memcg->res, the user counter. When the kernel memory > controller comes into play, we'll need to charge more than that. > > This is because kernel memory allocations will also draw from the user > counter, and can be bigger than a single page, as it is the case with > the stack (usually 2 pages) or some higher order slabs. > > [ [email protected]: added a changelog ] > > Signed-off-by: Suleiman Souhlal <[email protected]> > Signed-off-by: Glauber Costa <[email protected]> > Acked-by: David Rientjes <[email protected]> > Acked-by: Kamezawa Hiroyuki <[email protected]> > Acked-by: Michal Hocko <[email protected]>
Independent of how the per-subtree enable-through-setting-limit discussion pans out, we're going to need the charge cache, so: Acked-by: Johannes Weiner <[email protected]> _______________________________________________ Devel mailing list [email protected] https://openvz.org/mailman/listinfo/devel
