[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52005D92.1090103@huawei.com>
Date: Tue, 6 Aug 2013 10:21:06 +0800
From: Li Zefan <lizefan@...wei.com>
To: Tejun Heo <tj@...nel.org>
CC: <hannes@...xchg.org>, <mhocko@...e.cz>, <bsingharora@...il.com>,
<kamezawa.hiroyu@...fujitsu.com>, <cgroups@...r.kernel.org>,
<linux-mm@...ck.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 3/5] cgroup, memcg: move cgroup_event implementation
to memcg
On 2013/8/6 10:02, Li Zefan wrote:
>> static struct cftype mem_cgroup_files[] = {
>> {
>> .name = "usage_in_bytes",
>> @@ -5973,6 +6192,12 @@ static struct cftype mem_cgroup_files[] = {
>> .read_u64 = mem_cgroup_hierarchy_read,
>> },
>> {
>> + .name = "cgroup.event_control",
>> + .write_string = cgroup_write_event_control,
>> + .flags = CFTYPE_NO_PREFIX,
>> + .mode = S_IWUGO,
>> + },
>
> One of the misdesign of cgroup eventfd is, cgroup.event_control is
> totally redunant...
>
ok. write_string() is needed to accept arguments and pass them to
the event register function. still not good.
--
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