[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <491560C0.50400@linux.vnet.ibm.com>
Date: Sat, 08 Nov 2008 15:19:52 +0530
From: Balbir Singh <balbir@...ux.vnet.ibm.com>
To: Li Zefan <lizf@...fujitsu.com>
CC: linux-mm@...ck.org, YAMAMOTO Takashi <yamamoto@...inux.co.jp>,
Paul Menage <menage@...gle.com>, linux-kernel@...r.kernel.org,
Nick Piggin <nickpiggin@...oo.com.au>,
David Rientjes <rientjes@...gle.com>,
Pavel Emelianov <xemul@...nvz.org>,
Dhaval Giani <dhaval@...ux.vnet.ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Subject: Re: [RFC][mm] [PATCH 4/4] Memory cgroup hierarchy feature selector
(v2)
Li Zefan wrote:
>> +static int mem_cgroup_hierarchy_write(struct cgroup *cont, struct cftype *cft,
>> + u64 val)
>> +{
>> + int retval = 0;
>> + struct mem_cgroup *mem = mem_cgroup_from_cont(cont);
>> +
>> + if (val == 1) {
>> + if (list_empty(&cont->children))
>
> cgroup_lock should be held before checking cont->children.
>
Good point, I'll look at that aspect
>> + mem->use_hierarchy = val;
>> + else
>> + retval = -EBUSY;
>> + } else if (val == 0) {
>
> And code duplicate.
Yes, this can be optimized better. I'll fix that in v3.
>
>> + if (list_empty(&cont->children))
>> + mem->use_hierarchy nn= val;
>> + else
>> + retval = -EBUSY;
>> + } else
>> + retval = -EINVAL;
>> +
>> + return retval;
>> +}
>> +
>
--
Balbir
--
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