On Tue, Sep 18, 2012 at 06:03:58PM +0400, Glauber Costa wrote: > From: Suleiman Souhlal <ssouhlal@xxxxxxxxxxx> > > 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. > > [ glommer@xxxxxxxxxxxxx: added a changelog ] > > Signed-off-by: Suleiman Souhlal <suleiman@xxxxxxxxxx> > Signed-off-by: Glauber Costa <glommer@xxxxxxxxxxxxx> > Acked-by: David Rientjes <rientjes@xxxxxxxxxx> > Acked-by: Kamezawa Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx> > Acked-by: Michal Hocko <mhocko@xxxxxxx> 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 <hannes@xxxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
