From: Glauber Costa <glommer@parallels.com> To: <cgroups@vger.kernel.org> Cc: <linux-mm@kvack.org>, Andrew Morton <akpm@linux-foundation.org>, <linux-kernel@vger.kernel.org>, Frederic Weisbecker <fweisbec@gmail.com>, David Rientjes <rientjes@google.com>, Pekka Enberg <penberg@kernel.org>, Michal Hocko <mhocko@suse.cz>, Johannes Weiner <hannes@cmpxchg.org>, Christoph Lameter <cl@linux.com>, <devel@openvz.org>, <kamezawa.hiroyu@jp.fujitsu.com>, Tejun Heo <tj@kernel.org>, Glauber Costa <glommer@parallels.com> Subject: [PATCH 04/11] kmem slab accounting basic infrastructure Date: Mon, 25 Jun 2012 18:15:21 +0400 [thread overview] Message-ID: <1340633728-12785-5-git-send-email-glommer@parallels.com> (raw) In-Reply-To: <1340633728-12785-1-git-send-email-glommer@parallels.com> This patch adds the basic infrastructure for the accounting of the slab caches. To control that, the following files are created: * memory.kmem.usage_in_bytes * memory.kmem.limit_in_bytes * memory.kmem.failcnt * memory.kmem.max_usage_in_bytes They have the same meaning of their user memory counterparts. They reflect the state of the "kmem" res_counter. The code is not enabled until a limit is set. This can be tested by the flag "kmem_accounted". This means that after the patch is applied, no behavioral changes exists for whoever is still using memcg to control their memory usage. We always account to both user and kernel resource_counters. This effectively means that an independent kernel limit is in place when the limit is set to a lower value than the user memory. A equal or higher value means that the user limit will always hit first, meaning that kmem is effectively unlimited. People who want to track kernel memory but not limit it, can set this limit to a very high number (like RESOURCE_MAX - 1page - that no one will ever hit, or equal to the user memory) Signed-off-by: Glauber Costa <glommer@parallels.com> CC: Michal Hocko <mhocko@suse.cz> CC: Johannes Weiner <hannes@cmpxchg.org> Reviewed-by: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> --- mm/memcontrol.c | 78 ++++++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 77 insertions(+), 1 deletion(-) diff --git a/mm/memcontrol.c b/mm/memcontrol.c index 9352d40..6f34b77 100644 --- a/mm/memcontrol.c +++ b/mm/memcontrol.c @@ -265,6 +265,10 @@ struct mem_cgroup { }; /* + * the counter to account for kernel memory usage. + */ + struct res_counter kmem; + /* * Per cgroup active and inactive list, similar to the * per zone LRU lists. */ @@ -279,6 +283,7 @@ struct mem_cgroup { * Should the accounting and control be hierarchical, per subtree? */ bool use_hierarchy; + bool kmem_accounted; bool oom_lock; atomic_t under_oom; @@ -391,6 +396,7 @@ enum res_type { _MEM, _MEMSWAP, _OOM_TYPE, + _KMEM, }; #define MEMFILE_PRIVATE(x, val) ((x) << 16 | (val)) @@ -1438,6 +1444,10 @@ done: res_counter_read_u64(&memcg->memsw, RES_USAGE) >> 10, res_counter_read_u64(&memcg->memsw, RES_LIMIT) >> 10, res_counter_read_u64(&memcg->memsw, RES_FAILCNT)); + printk(KERN_INFO "kmem: usage %llukB, limit %llukB, failcnt %llu\n", + res_counter_read_u64(&memcg->kmem, RES_USAGE) >> 10, + res_counter_read_u64(&memcg->kmem, RES_LIMIT) >> 10, + res_counter_read_u64(&memcg->kmem, RES_FAILCNT)); } /* @@ -3879,6 +3889,11 @@ static ssize_t mem_cgroup_read(struct cgroup *cont, struct cftype *cft, else val = res_counter_read_u64(&memcg->memsw, name); break; +#ifdef CONFIG_CGROUP_MEM_RES_CTLR_KMEM + case _KMEM: + val = res_counter_read_u64(&memcg->kmem, name); + break; +#endif default: BUG(); } @@ -3916,8 +3931,26 @@ static int mem_cgroup_write(struct cgroup *cont, struct cftype *cft, break; if (type == _MEM) ret = mem_cgroup_resize_limit(memcg, val); - else + else if (type == _MEMSWAP) ret = mem_cgroup_resize_memsw_limit(memcg, val); +#ifdef CONFIG_CGROUP_MEM_RES_CTLR_KMEM + else if (type == _KMEM) { + ret = res_counter_set_limit(&memcg->kmem, val); + if (ret) + break; + /* + * Once enabled, can't be disabled. We could in theory + * disable it if we haven't yet created any caches, or + * if we can shrink them all to death. + * + * But it is not worth the trouble + */ + if (!memcg->kmem_accounted && val != RESOURCE_MAX) + memcg->kmem_accounted = true; + } +#endif + else + return -EINVAL; break; case RES_SOFT_LIMIT: ret = res_counter_memparse_write_strategy(buffer, &val); @@ -3982,12 +4015,20 @@ static int mem_cgroup_reset(struct cgroup *cont, unsigned int event) case RES_MAX_USAGE: if (type == _MEM) res_counter_reset_max(&memcg->res); +#ifdef CONFIG_CGROUP_MEM_RES_CTLR_KMEM + else if (type == _KMEM) + res_counter_reset_max(&memcg->kmem); +#endif else res_counter_reset_max(&memcg->memsw); break; case RES_FAILCNT: if (type == _MEM) res_counter_reset_failcnt(&memcg->res); +#ifdef CONFIG_CGROUP_MEM_RES_CTLR_KMEM + else if (type == _KMEM) + res_counter_reset_failcnt(&memcg->kmem); +#endif else res_counter_reset_failcnt(&memcg->memsw); break; @@ -4549,6 +4590,33 @@ static int mem_cgroup_oom_control_write(struct cgroup *cgrp, } #ifdef CONFIG_CGROUP_MEM_RES_CTLR_KMEM +static struct cftype kmem_cgroup_files[] = { + { + .name = "kmem.limit_in_bytes", + .private = MEMFILE_PRIVATE(_KMEM, RES_LIMIT), + .write_string = mem_cgroup_write, + .read = mem_cgroup_read, + }, + { + .name = "kmem.usage_in_bytes", + .private = MEMFILE_PRIVATE(_KMEM, RES_USAGE), + .read = mem_cgroup_read, + }, + { + .name = "kmem.failcnt", + .private = MEMFILE_PRIVATE(_KMEM, RES_FAILCNT), + .trigger = mem_cgroup_reset, + .read = mem_cgroup_read, + }, + { + .name = "kmem.max_usage_in_bytes", + .private = MEMFILE_PRIVATE(_KMEM, RES_MAX_USAGE), + .trigger = mem_cgroup_reset, + .read = mem_cgroup_read, + }, + {}, +}; + static int memcg_init_kmem(struct mem_cgroup *memcg, struct cgroup_subsys *ss) { return mem_cgroup_sockets_init(memcg, ss); @@ -4892,6 +4960,12 @@ mem_cgroup_create(struct cgroup *cont) int cpu; enable_swap_cgroup(); parent = NULL; + +#ifdef CONFIG_CGROUP_MEM_RES_CTLR_KMEM + WARN_ON(cgroup_add_cftypes(&mem_cgroup_subsys, + kmem_cgroup_files)); +#endif + if (mem_cgroup_soft_limit_tree_init()) goto free_out; root_mem_cgroup = memcg; @@ -4910,6 +4984,7 @@ mem_cgroup_create(struct cgroup *cont) if (parent && parent->use_hierarchy) { res_counter_init(&memcg->res, &parent->res); res_counter_init(&memcg->memsw, &parent->memsw); + res_counter_init(&memcg->kmem, &parent->kmem); /* * We increment refcnt of the parent to ensure that we can * safely access it on res_counter_charge/uncharge. @@ -4920,6 +4995,7 @@ mem_cgroup_create(struct cgroup *cont) } else { res_counter_init(&memcg->res, NULL); res_counter_init(&memcg->memsw, NULL); + res_counter_init(&memcg->kmem, NULL); } memcg->last_scanned_node = MAX_NUMNODES; INIT_LIST_HEAD(&memcg->oom_notify); -- 1.7.10.2
WARNING: multiple messages have this Message-ID (diff)
From: Glauber Costa <glommer@parallels.com> To: cgroups@vger.kernel.org Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org, Frederic Weisbecker <fweisbec@gmail.com>, David Rientjes <rientjes@google.com>, Pekka Enberg <penberg@kernel.org>, Michal Hocko <mhocko@suse.cz>, Johannes Weiner <hannes@cmpxchg.org>, Christoph Lameter <cl@linux.com>, devel@openvz.org, kamezawa.hiroyu@jp.fujitsu.com, Tejun Heo <tj@kernel.org>, Glauber Costa <glommer@parallels.com> Subject: [PATCH 04/11] kmem slab accounting basic infrastructure Date: Mon, 25 Jun 2012 18:15:21 +0400 [thread overview] Message-ID: <1340633728-12785-5-git-send-email-glommer@parallels.com> (raw) In-Reply-To: <1340633728-12785-1-git-send-email-glommer@parallels.com> This patch adds the basic infrastructure for the accounting of the slab caches. To control that, the following files are created: * memory.kmem.usage_in_bytes * memory.kmem.limit_in_bytes * memory.kmem.failcnt * memory.kmem.max_usage_in_bytes They have the same meaning of their user memory counterparts. They reflect the state of the "kmem" res_counter. The code is not enabled until a limit is set. This can be tested by the flag "kmem_accounted". This means that after the patch is applied, no behavioral changes exists for whoever is still using memcg to control their memory usage. We always account to both user and kernel resource_counters. This effectively means that an independent kernel limit is in place when the limit is set to a lower value than the user memory. A equal or higher value means that the user limit will always hit first, meaning that kmem is effectively unlimited. People who want to track kernel memory but not limit it, can set this limit to a very high number (like RESOURCE_MAX - 1page - that no one will ever hit, or equal to the user memory) Signed-off-by: Glauber Costa <glommer@parallels.com> CC: Michal Hocko <mhocko@suse.cz> CC: Johannes Weiner <hannes@cmpxchg.org> Reviewed-by: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> --- mm/memcontrol.c | 78 ++++++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 77 insertions(+), 1 deletion(-) diff --git a/mm/memcontrol.c b/mm/memcontrol.c index 9352d40..6f34b77 100644 --- a/mm/memcontrol.c +++ b/mm/memcontrol.c @@ -265,6 +265,10 @@ struct mem_cgroup { }; /* + * the counter to account for kernel memory usage. + */ + struct res_counter kmem; + /* * Per cgroup active and inactive list, similar to the * per zone LRU lists. */ @@ -279,6 +283,7 @@ struct mem_cgroup { * Should the accounting and control be hierarchical, per subtree? */ bool use_hierarchy; + bool kmem_accounted; bool oom_lock; atomic_t under_oom; @@ -391,6 +396,7 @@ enum res_type { _MEM, _MEMSWAP, _OOM_TYPE, + _KMEM, }; #define MEMFILE_PRIVATE(x, val) ((x) << 16 | (val)) @@ -1438,6 +1444,10 @@ done: res_counter_read_u64(&memcg->memsw, RES_USAGE) >> 10, res_counter_read_u64(&memcg->memsw, RES_LIMIT) >> 10, res_counter_read_u64(&memcg->memsw, RES_FAILCNT)); + printk(KERN_INFO "kmem: usage %llukB, limit %llukB, failcnt %llu\n", + res_counter_read_u64(&memcg->kmem, RES_USAGE) >> 10, + res_counter_read_u64(&memcg->kmem, RES_LIMIT) >> 10, + res_counter_read_u64(&memcg->kmem, RES_FAILCNT)); } /* @@ -3879,6 +3889,11 @@ static ssize_t mem_cgroup_read(struct cgroup *cont, struct cftype *cft, else val = res_counter_read_u64(&memcg->memsw, name); break; +#ifdef CONFIG_CGROUP_MEM_RES_CTLR_KMEM + case _KMEM: + val = res_counter_read_u64(&memcg->kmem, name); + break; +#endif default: BUG(); } @@ -3916,8 +3931,26 @@ static int mem_cgroup_write(struct cgroup *cont, struct cftype *cft, break; if (type == _MEM) ret = mem_cgroup_resize_limit(memcg, val); - else + else if (type == _MEMSWAP) ret = mem_cgroup_resize_memsw_limit(memcg, val); +#ifdef CONFIG_CGROUP_MEM_RES_CTLR_KMEM + else if (type == _KMEM) { + ret = res_counter_set_limit(&memcg->kmem, val); + if (ret) + break; + /* + * Once enabled, can't be disabled. We could in theory + * disable it if we haven't yet created any caches, or + * if we can shrink them all to death. + * + * But it is not worth the trouble + */ + if (!memcg->kmem_accounted && val != RESOURCE_MAX) + memcg->kmem_accounted = true; + } +#endif + else + return -EINVAL; break; case RES_SOFT_LIMIT: ret = res_counter_memparse_write_strategy(buffer, &val); @@ -3982,12 +4015,20 @@ static int mem_cgroup_reset(struct cgroup *cont, unsigned int event) case RES_MAX_USAGE: if (type == _MEM) res_counter_reset_max(&memcg->res); +#ifdef CONFIG_CGROUP_MEM_RES_CTLR_KMEM + else if (type == _KMEM) + res_counter_reset_max(&memcg->kmem); +#endif else res_counter_reset_max(&memcg->memsw); break; case RES_FAILCNT: if (type == _MEM) res_counter_reset_failcnt(&memcg->res); +#ifdef CONFIG_CGROUP_MEM_RES_CTLR_KMEM + else if (type == _KMEM) + res_counter_reset_failcnt(&memcg->kmem); +#endif else res_counter_reset_failcnt(&memcg->memsw); break; @@ -4549,6 +4590,33 @@ static int mem_cgroup_oom_control_write(struct cgroup *cgrp, } #ifdef CONFIG_CGROUP_MEM_RES_CTLR_KMEM +static struct cftype kmem_cgroup_files[] = { + { + .name = "kmem.limit_in_bytes", + .private = MEMFILE_PRIVATE(_KMEM, RES_LIMIT), + .write_string = mem_cgroup_write, + .read = mem_cgroup_read, + }, + { + .name = "kmem.usage_in_bytes", + .private = MEMFILE_PRIVATE(_KMEM, RES_USAGE), + .read = mem_cgroup_read, + }, + { + .name = "kmem.failcnt", + .private = MEMFILE_PRIVATE(_KMEM, RES_FAILCNT), + .trigger = mem_cgroup_reset, + .read = mem_cgroup_read, + }, + { + .name = "kmem.max_usage_in_bytes", + .private = MEMFILE_PRIVATE(_KMEM, RES_MAX_USAGE), + .trigger = mem_cgroup_reset, + .read = mem_cgroup_read, + }, + {}, +}; + static int memcg_init_kmem(struct mem_cgroup *memcg, struct cgroup_subsys *ss) { return mem_cgroup_sockets_init(memcg, ss); @@ -4892,6 +4960,12 @@ mem_cgroup_create(struct cgroup *cont) int cpu; enable_swap_cgroup(); parent = NULL; + +#ifdef CONFIG_CGROUP_MEM_RES_CTLR_KMEM + WARN_ON(cgroup_add_cftypes(&mem_cgroup_subsys, + kmem_cgroup_files)); +#endif + if (mem_cgroup_soft_limit_tree_init()) goto free_out; root_mem_cgroup = memcg; @@ -4910,6 +4984,7 @@ mem_cgroup_create(struct cgroup *cont) if (parent && parent->use_hierarchy) { res_counter_init(&memcg->res, &parent->res); res_counter_init(&memcg->memsw, &parent->memsw); + res_counter_init(&memcg->kmem, &parent->kmem); /* * We increment refcnt of the parent to ensure that we can * safely access it on res_counter_charge/uncharge. @@ -4920,6 +4995,7 @@ mem_cgroup_create(struct cgroup *cont) } else { res_counter_init(&memcg->res, NULL); res_counter_init(&memcg->memsw, NULL); + res_counter_init(&memcg->kmem, NULL); } memcg->last_scanned_node = MAX_NUMNODES; INIT_LIST_HEAD(&memcg->oom_notify); -- 1.7.10.2 -- 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>
next prev parent reply other threads:[~2012-06-25 14:18 UTC|newest] Thread overview: 238+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-25 14:15 [PATCH 00/11] kmem controller for memcg: stripped down version Glauber Costa 2012-06-25 14:15 ` Glauber Costa 2012-06-25 14:15 ` Glauber Costa 2012-06-25 14:15 ` [PATCH 01/11] memcg: Make it possible to use the stock for more than one page Glauber Costa 2012-06-25 14:15 ` Glauber Costa 2012-06-25 14:15 ` Glauber Costa 2012-06-25 17:44 ` Tejun Heo 2012-06-25 17:44 ` Tejun Heo 2012-06-25 17:44 ` Tejun Heo 2012-06-25 22:29 ` Glauber Costa 2012-06-25 22:29 ` Glauber Costa 2012-06-25 22:33 ` Tejun Heo 2012-06-25 22:33 ` Tejun Heo 2012-06-26 4:01 ` David Rientjes 2012-06-26 4:01 ` David Rientjes 2012-06-25 14:15 ` [PATCH 02/11] memcg: Reclaim when more than one page needed Glauber Costa 2012-06-25 14:15 ` Glauber Costa 2012-06-25 23:33 ` Suleiman Souhlal 2012-06-25 23:33 ` Suleiman Souhlal 2012-06-26 8:39 ` Glauber Costa 2012-06-26 8:39 ` Glauber Costa 2012-06-27 16:16 ` Suleiman Souhlal 2012-06-27 16:16 ` Suleiman Souhlal 2012-06-27 16:16 ` Suleiman Souhlal 2012-06-26 4:09 ` David Rientjes 2012-06-26 4:09 ` David Rientjes 2012-06-26 7:12 ` Glauber Costa 2012-06-26 7:12 ` Glauber Costa 2012-06-26 7:12 ` Glauber Costa 2012-06-26 8:54 ` David Rientjes 2012-06-26 8:54 ` David Rientjes 2012-06-26 8:54 ` David Rientjes 2012-06-26 9:08 ` Glauber Costa 2012-06-26 9:08 ` Glauber Costa 2012-06-26 9:17 ` David Rientjes 2012-06-26 9:17 ` David Rientjes 2012-06-26 9:23 ` Glauber Costa 2012-06-26 9:23 ` Glauber Costa 2012-06-27 10:03 ` Glauber Costa 2012-06-27 10:03 ` Glauber Costa 2012-06-27 19:48 ` David Rientjes 2012-06-27 19:48 ` David Rientjes 2012-06-27 19:48 ` David Rientjes 2012-06-27 20:47 ` Glauber Costa 2012-06-27 20:47 ` Glauber Costa 2012-06-25 14:15 ` [PATCH 03/11] memcg: change defines to an enum Glauber Costa 2012-06-25 14:15 ` Glauber Costa 2012-06-26 4:11 ` David Rientjes 2012-06-26 4:11 ` David Rientjes 2012-06-26 8:28 ` Glauber Costa 2012-06-26 8:28 ` Glauber Costa 2012-06-26 9:01 ` David Rientjes 2012-06-26 9:01 ` David Rientjes 2012-06-26 9:01 ` David Rientjes 2012-06-25 14:15 ` Glauber Costa [this message] 2012-06-25 14:15 ` [PATCH 04/11] kmem slab accounting basic infrastructure Glauber Costa 2012-06-26 4:22 ` David Rientjes 2012-06-26 4:22 ` David Rientjes 2012-06-26 7:09 ` Glauber Costa 2012-06-26 7:09 ` Glauber Costa 2012-06-25 14:15 ` [PATCH 05/11] Add a __GFP_KMEMCG flag Glauber Costa 2012-06-25 14:15 ` Glauber Costa 2012-06-26 4:25 ` David Rientjes 2012-06-26 4:25 ` David Rientjes 2012-06-26 7:08 ` Glauber Costa 2012-06-26 7:08 ` Glauber Costa 2012-06-26 9:03 ` David Rientjes 2012-06-26 9:03 ` David Rientjes 2012-06-25 14:15 ` [PATCH 06/11] memcg: kmem controller infrastructure Glauber Costa 2012-06-25 14:15 ` Glauber Costa 2012-06-25 14:15 ` Glauber Costa 2012-06-25 18:06 ` Tejun Heo 2012-06-25 18:06 ` Tejun Heo 2012-06-25 18:06 ` Tejun Heo 2012-06-25 22:28 ` Glauber Costa 2012-06-25 22:28 ` Glauber Costa 2012-06-25 23:17 ` Andrew Morton 2012-06-25 23:17 ` Andrew Morton 2012-06-25 23:17 ` Andrew Morton 2012-06-26 14:40 ` Glauber Costa 2012-06-26 14:40 ` Glauber Costa 2012-06-26 15:01 ` Glauber Costa 2012-06-26 15:01 ` Glauber Costa 2012-06-26 15:01 ` Glauber Costa 2012-06-26 18:01 ` Andrew Morton 2012-06-26 18:01 ` Andrew Morton 2012-06-26 18:01 ` Andrew Morton 2012-06-26 18:08 ` Tejun Heo 2012-06-26 18:08 ` Tejun Heo 2012-06-26 18:08 ` Tejun Heo 2012-06-26 18:14 ` Glauber Costa 2012-06-26 18:14 ` Glauber Costa 2012-06-26 19:20 ` Andrew Morton 2012-06-26 19:20 ` Andrew Morton 2012-06-26 15:29 ` Glauber Costa 2012-06-26 15:29 ` Glauber Costa 2012-06-26 15:29 ` Glauber Costa 2012-06-26 9:12 ` David Rientjes 2012-06-26 9:12 ` David Rientjes 2012-06-26 9:12 ` David Rientjes 2012-06-26 9:17 ` Glauber Costa 2012-06-26 9:17 ` Glauber Costa 2012-06-26 9:17 ` Glauber Costa 2012-06-27 4:01 ` David Rientjes 2012-06-27 4:01 ` David Rientjes 2012-06-27 9:33 ` Glauber Costa 2012-06-27 9:33 ` Glauber Costa 2012-06-27 9:33 ` Glauber Costa 2012-06-27 19:46 ` David Rientjes 2012-06-27 19:46 ` David Rientjes 2012-06-25 14:15 ` [PATCH 07/11] mm: Allocate kernel pages to the right memcg Glauber Costa 2012-06-25 14:15 ` Glauber Costa 2012-06-25 14:15 ` Glauber Costa 2012-06-25 18:07 ` Tejun Heo 2012-06-25 18:07 ` Tejun Heo 2012-06-25 22:27 ` Glauber Costa 2012-06-25 22:27 ` Glauber Costa 2012-06-25 14:15 ` [PATCH 08/11] memcg: disable kmem code when not in use Glauber Costa 2012-06-25 14:15 ` Glauber Costa 2012-06-25 14:15 ` Glauber Costa 2012-06-26 5:51 ` Kamezawa Hiroyuki 2012-06-26 5:51 ` Kamezawa Hiroyuki 2012-06-25 14:15 ` [PATCH 09/11] memcg: propagate kmem limiting information to children Glauber Costa 2012-06-25 14:15 ` Glauber Costa 2012-06-25 14:15 ` Glauber Costa 2012-06-25 18:29 ` Tejun Heo 2012-06-25 18:29 ` Tejun Heo 2012-06-25 22:36 ` Glauber Costa 2012-06-25 22:36 ` Glauber Costa 2012-06-25 22:36 ` Glauber Costa 2012-06-25 22:49 ` Tejun Heo 2012-06-25 22:49 ` Tejun Heo 2012-06-25 22:49 ` Tejun Heo 2012-06-25 23:21 ` Andrew Morton 2012-06-25 23:21 ` Andrew Morton 2012-06-26 5:23 ` David Rientjes 2012-06-26 5:23 ` David Rientjes 2012-06-25 23:23 ` Andrew Morton 2012-06-25 23:23 ` Andrew Morton 2012-06-26 5:24 ` David Rientjes 2012-06-26 5:24 ` David Rientjes 2012-06-26 5:31 ` Andrew Morton 2012-06-26 5:31 ` Andrew Morton 2012-06-26 5:31 ` Andrew Morton 2012-06-26 7:23 ` Glauber Costa 2012-06-26 7:23 ` Glauber Costa 2012-06-26 7:23 ` Glauber Costa 2012-06-25 14:15 ` [PATCH 10/11] memcg: allow a memcg with kmem charges to be destructed Glauber Costa 2012-06-25 14:15 ` Glauber Costa 2012-06-25 14:15 ` Glauber Costa 2012-06-25 18:34 ` Tejun Heo 2012-06-25 18:34 ` Tejun Heo 2012-06-25 22:25 ` Glauber Costa 2012-06-25 22:25 ` Glauber Costa 2012-06-25 22:25 ` Glauber Costa 2012-06-26 5:59 ` Kamezawa Hiroyuki 2012-06-26 5:59 ` Kamezawa Hiroyuki 2012-06-26 7:21 ` Glauber Costa 2012-06-26 7:21 ` Glauber Costa 2012-06-26 7:21 ` Glauber Costa 2012-06-25 14:15 ` [PATCH 11/11] protect architectures where THREAD_SIZE >= PAGE_SIZE against fork bombs Glauber Costa 2012-06-25 14:15 ` Glauber Costa 2012-06-25 14:15 ` Glauber Costa 2012-06-25 16:55 ` Frederic Weisbecker 2012-06-25 16:55 ` Frederic Weisbecker 2012-06-25 18:38 ` Tejun Heo 2012-06-25 18:38 ` Tejun Heo 2012-06-25 18:38 ` Tejun Heo 2012-06-25 20:57 ` Frederic Weisbecker 2012-06-25 20:57 ` Frederic Weisbecker 2012-06-25 20:57 ` Frederic Weisbecker 2012-06-26 12:48 ` Glauber Costa 2012-06-26 12:48 ` Glauber Costa 2012-06-26 12:48 ` Glauber Costa 2012-06-26 13:38 ` Frederic Weisbecker 2012-06-26 13:38 ` Frederic Weisbecker 2012-06-26 13:38 ` Frederic Weisbecker 2012-06-26 13:37 ` Glauber Costa 2012-06-26 13:37 ` Glauber Costa 2012-06-26 13:37 ` Glauber Costa 2012-06-26 13:44 ` Frederic Weisbecker 2012-06-26 13:44 ` Frederic Weisbecker 2012-06-26 13:44 ` Frederic Weisbecker 2012-06-26 4:57 ` David Rientjes 2012-06-26 4:57 ` David Rientjes 2012-06-26 5:35 ` Kamezawa Hiroyuki 2012-06-26 5:35 ` Kamezawa Hiroyuki 2012-06-26 5:35 ` Kamezawa Hiroyuki 2012-06-26 7:23 ` Glauber Costa 2012-06-26 7:23 ` Glauber Costa 2012-06-26 7:23 ` Glauber Costa 2012-06-26 8:45 ` David Rientjes 2012-06-26 8:45 ` David Rientjes 2012-06-26 8:45 ` David Rientjes 2012-06-26 8:44 ` Glauber Costa 2012-06-26 8:44 ` Glauber Costa 2012-06-26 8:44 ` Glauber Costa 2012-06-26 9:05 ` David Rientjes 2012-06-26 9:05 ` David Rientjes 2012-06-25 23:27 ` [PATCH 00/11] kmem controller for memcg: stripped down version Andrew Morton 2012-06-25 23:27 ` Andrew Morton 2012-06-26 7:17 ` Glauber Costa 2012-06-26 7:17 ` Glauber Costa 2012-06-26 21:55 ` Andrew Morton 2012-06-26 21:55 ` Andrew Morton 2012-06-26 21:55 ` Andrew Morton 2012-06-27 1:08 ` David Rientjes 2012-06-27 1:08 ` David Rientjes 2012-06-27 8:39 ` Glauber Costa 2012-06-27 8:39 ` Glauber Costa 2012-06-27 8:39 ` Glauber Costa 2012-06-27 9:29 ` Fork bomb limitation in memcg WAS: " Glauber Costa 2012-06-27 9:29 ` Glauber Costa 2012-06-27 9:29 ` Glauber Costa 2012-06-27 12:29 ` Frederic Weisbecker 2012-06-27 12:29 ` Frederic Weisbecker 2012-06-27 12:28 ` Glauber Costa 2012-06-27 12:28 ` Glauber Costa 2012-06-27 12:35 ` Frederic Weisbecker 2012-06-27 12:35 ` Frederic Weisbecker 2012-06-27 19:38 ` David Rientjes 2012-06-27 19:38 ` David Rientjes 2012-06-27 19:38 ` David Rientjes 2012-06-28 9:01 ` Glauber Costa 2012-06-28 9:01 ` Glauber Costa 2012-06-28 22:25 ` Andrew Morton 2012-06-28 22:25 ` Andrew Morton 2012-07-03 11:38 ` Glauber Costa 2012-07-03 11:38 ` Glauber Costa 2012-07-03 11:38 ` Glauber Costa 2012-07-12 15:40 ` Frederic Weisbecker 2012-07-12 15:40 ` Frederic Weisbecker 2012-08-07 13:59 ` Glauber Costa 2012-08-07 13:59 ` Glauber Costa 2012-08-07 13:59 ` Glauber Costa 2012-08-08 14:15 ` Glauber Costa 2012-08-08 14:15 ` Glauber Costa 2012-08-08 14:15 ` Glauber Costa
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1340633728-12785-5-git-send-email-glommer@parallels.com \ --to=glommer@parallels.com \ --cc=akpm@linux-foundation.org \ --cc=cgroups@vger.kernel.org \ --cc=cl@linux.com \ --cc=devel@openvz.org \ --cc=fweisbec@gmail.com \ --cc=hannes@cmpxchg.org \ --cc=kamezawa.hiroyu@jp.fujitsu.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=mhocko@suse.cz \ --cc=penberg@kernel.org \ --cc=rientjes@google.com \ --cc=tj@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.