On Wed, 7 Mar 2012 13:43:05 -0800 (PST) David Rientjes <rientjes@xxxxxxxxxx> wrote: > The oom killer typically displays the allocation order at the time of oom > as a part of its diangostic messages (for global, cpuset, and mempolicy > ooms). > > The memory controller may also pass the charge order to the oom killer so > it can emit the same information. This is useful in determining how > large the memory allocation is that triggered the oom killer. > > Signed-off-by: David Rientjes <rientjes@xxxxxxxxxx> Now, usual memcg only supports 1 page allocation. (If hugetlb allocation failed, it will use a normal page allocation.) But it seems there are(will be) changes because of tcp buffer control or slab accounting. Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx> -- 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
