[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <491D1A17.2060404@cn.fujitsu.com>
Date: Fri, 14 Nov 2008 14:26:31 +0800
From: Li Zefan <lizf@...fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
CC: Andrew Morton <akpm@...ux-foundation.org>,
Jan Blunck <jblunck@...e.de>, containers@...ts.osdl.org,
Linux-Kernel Mailinglist <linux-kernel@...r.kernel.org>,
Balbir Singh <balbir@...ux.vnet.ibm.com>
Subject: Re: [PATCH] memcg: reduce size of per-cpu-stat to be appropriate
size.
KAMEZAWA Hiroyuki wrote:
> How about this one ?
> tested on x86-64 + mmotm-Nov10, works well.
> (test on other arch is welcome.)
>
> -Kame
> ==
> As Jan Blunck <jblunck@...e.de> pointed out, allocating
> per-cpu stat for memcg to the size of NR_CPUS is not good.
>
> This patch changes mem_cgroup's cpustat allocation not based
> on NR_CPUS but based on nr_cpu_ids.
>
> From: Jan Blunck <jblunck@...e.de>
> Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
>
Looks good :) . It's ok to use nr_cpu_ids when cgroup_init() is called
at boot.
Reviewed-by: Li Zefan <lizf@...fujitsu.com>
except..see comments for mem_cgroup_create()
> +static int mem_cgroup_size(void)
> +{
> + int cpustat_size = nr_cpu_ids * sizeof(struct mem_cgroup_stat_cpu);
> + return sizeof(struct mem_cgroup) + cpustat_size;
> +}
> +
> +
minor comment: one empty line is suffice.
...
> static struct cgroup_subsys_state *
> mem_cgroup_create(struct cgroup_subsys *ss, struct cgroup *cont)
> {
> struct mem_cgroup *mem;
> int node;
>
> - if (unlikely((cont->parent) == NULL)) {
> - mem = &init_mem_cgroup;
> - } else {
> - mem = mem_cgroup_alloc();
> - if (!mem)
> - return ERR_PTR(-ENOMEM);
> - }
> + mem = mem_cgroup_alloc();
> + if (!mem)
> + return ERR_PTR(-ENOMEM);
>
> res_counter_init(&mem->res);
>
free_out:
for_each_node_state(node, N_POSSIBLE)
free_mem_cgroup_per_zone_info(mem, node);
if (cont->parent != NULL) <---- this check should be removed
mem_cgroup_free(mem);
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists