On Tue, 16 Oct 2012, Glauber Costa wrote: > When a process tries to allocate a page with the __GFP_KMEMCG flag, the > page allocator will call the corresponding memcg functions to validate > the allocation. Tasks in the root memcg can always proceed. > > To avoid adding markers to the page - and a kmem flag that would > necessarily follow, as much as doing page_cgroup lookups for no reason, > whoever is marking its allocations with __GFP_KMEMCG flag is responsible > for telling the page allocator that this is such an allocation at > free_pages() time. This is done by the invocation of > __free_accounted_pages() and free_accounted_pages(). > > [ v2: inverted test order to avoid a memcg_get leak, > free_accounted_pages simplification ] > [ v4: test for TIF_MEMDIE at newpage_charge ] > > Signed-off-by: Glauber Costa <[email protected]> > Acked-by: Michal Hocko <[email protected]> > Acked-by: Mel Gorman <[email protected]> > Acked-by: Kamezawa Hiroyuki <[email protected]> > CC: Christoph Lameter <[email protected]> > CC: Pekka Enberg <[email protected]> > CC: Johannes Weiner <[email protected]> > CC: Suleiman Souhlal <[email protected]> > CC: Tejun Heo <[email protected]>
Acked-by: David Rientjes <[email protected]> -- 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/
