Re: [PATCH 09/11] memcg: propagate kmem limiting information to children
From: Andrew Morton <akpm@linux-foundation.org>
Date: 2012-06-25 23:23:55
Also in:
linux-mm, lkml
On Mon, 25 Jun 2012 18:15:26 +0400 Glauber Costa [off-list ref] wrote:
quoted hunk ↗ jump to hunk
--- a/mm/memcontrol.c +++ b/mm/memcontrol.c@@ -287,7 +287,11 @@ struct mem_cgroup { * Should the accounting and control be hierarchical, per subtree? */ bool use_hierarchy; - bool kmem_accounted; + /* + * bit0: accounted by this cgroup + * bit1: accounted by a parent. + */ + volatile unsigned long kmem_accounted;
I suggest unsigned long kmem_accounted; /* See KMEM_ACCOUNTED_*, below */
quoted hunk ↗ jump to hunk
bool oom_lock; atomic_t under_oom;@@ -340,6 +344,9 @@ struct mem_cgroup { #endif }; +#define KMEM_ACCOUNTED_THIS 0 +#define KMEM_ACCOUNTED_PARENT 1
And then document the fields here. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>