From: Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
Glauber Costa <glommer-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>,
KAMEZAWA Hiroyuki
<kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>,
Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>,
Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Cgroups <cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org
Subject: Re: [PATCH v3 2/8] cgroup: document how cgroup IDs are assigned
Date: Tue, 30 Jul 2013 09:08:14 +0800 [thread overview]
Message-ID: <51F711FE.3040006@huawei.com> (raw)
In-Reply-To: <20130729182632.GC26076-9pTldWuhBndy/B6EtB590w@public.gmane.org>
On 2013/7/30 2:26, Tejun Heo wrote:
> On Mon, Jul 29, 2013 at 03:08:04PM +0800, Li Zefan wrote:
>> As cgroup id has been used in netprio cgroup and will be used in memcg,
>> it's important to make it clear how a cgroup id is allocated.
>>
>> For example, in netprio cgroup, the id is used as index of anarray.
>>
>> Signed-off-by: Li Zefan <lizefan-Z5rXVj2qdvIAvxtiuMwx3w@public.gmane.org>
>> Reviewed-by: Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>
>
> We can merge this into the first patch?
>
The first patch just changes ida to idr, it doesn't change how IDs are
allocated, so I prefer make this a standalone patch.
WARNING: multiple messages have this Message-ID (diff)
From: Li Zefan <lizefan@huawei.com>
To: Tejun Heo <tj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Glauber Costa <glommer@parallels.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Michal Hocko <mhocko@suse.cz>,
Johannes Weiner <hannes@cmpxchg.org>,
LKML <linux-kernel@vger.kernel.org>,
Cgroups <cgroups@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: [PATCH v3 2/8] cgroup: document how cgroup IDs are assigned
Date: Tue, 30 Jul 2013 09:08:14 +0800 [thread overview]
Message-ID: <51F711FE.3040006@huawei.com> (raw)
In-Reply-To: <20130729182632.GC26076@mtj.dyndns.org>
On 2013/7/30 2:26, Tejun Heo wrote:
> On Mon, Jul 29, 2013 at 03:08:04PM +0800, Li Zefan wrote:
>> As cgroup id has been used in netprio cgroup and will be used in memcg,
>> it's important to make it clear how a cgroup id is allocated.
>>
>> For example, in netprio cgroup, the id is used as index of anarray.
>>
>> Signed-off-by: Li Zefan <lizefan@huwei.com>
>> Reviewed-by: Michal Hocko <mhocko@suse.cz>
>
> We can merge this into the first patch?
>
The first patch just changes ida to idr, it doesn't change how IDs are
allocated, so I prefer make this a standalone patch.
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Li Zefan <lizefan@huawei.com>
To: Tejun Heo <tj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Glauber Costa <glommer@parallels.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Michal Hocko <mhocko@suse.cz>,
Johannes Weiner <hannes@cmpxchg.org>,
LKML <linux-kernel@vger.kernel.org>,
Cgroups <cgroups@vger.kernel.org>, <linux-mm@kvack.org>
Subject: Re: [PATCH v3 2/8] cgroup: document how cgroup IDs are assigned
Date: Tue, 30 Jul 2013 09:08:14 +0800 [thread overview]
Message-ID: <51F711FE.3040006@huawei.com> (raw)
In-Reply-To: <20130729182632.GC26076@mtj.dyndns.org>
On 2013/7/30 2:26, Tejun Heo wrote:
> On Mon, Jul 29, 2013 at 03:08:04PM +0800, Li Zefan wrote:
>> As cgroup id has been used in netprio cgroup and will be used in memcg,
>> it's important to make it clear how a cgroup id is allocated.
>>
>> For example, in netprio cgroup, the id is used as index of anarray.
>>
>> Signed-off-by: Li Zefan <lizefan@huwei.com>
>> Reviewed-by: Michal Hocko <mhocko@suse.cz>
>
> We can merge this into the first patch?
>
The first patch just changes ida to idr, it doesn't change how IDs are
allocated, so I prefer make this a standalone patch.
next prev parent reply other threads:[~2013-07-30 1:08 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 7:07 [PATCH v3 0/8] memcg, cgroup: kill css_id Li Zefan
2013-07-29 7:07 ` Li Zefan
2013-07-29 7:08 ` [PATCH v3 2/8] cgroup: document how cgroup IDs are assigned Li Zefan
2013-07-29 7:08 ` Li Zefan
2013-07-29 18:26 ` Tejun Heo
2013-07-29 18:26 ` Tejun Heo
[not found] ` <20130729182632.GC26076-9pTldWuhBndy/B6EtB590w@public.gmane.org>
2013-07-30 1:08 ` Li Zefan [this message]
2013-07-30 1:08 ` Li Zefan
2013-07-30 1:08 ` Li Zefan
2013-07-30 14:22 ` Tejun Heo
2013-07-30 14:22 ` Tejun Heo
2013-07-29 7:08 ` [PATCH v3 3/8] cgroup: implement cgroup_from_id() Li Zefan
2013-07-29 7:08 ` Li Zefan
2013-07-29 18:31 ` Tejun Heo
2013-07-29 18:31 ` Tejun Heo
2013-07-29 7:08 ` [PATCH v3 4/8] memcg: convert to use cgroup_is_descendant() Li Zefan
2013-07-29 7:08 ` Li Zefan
2013-07-29 7:08 ` [PATCH v3 5/8] memcg: convert to use cgroup id Li Zefan
2013-07-29 7:08 ` Li Zefan
[not found] ` <51F614B2.6010503-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2013-07-29 7:07 ` [PATCH v3 1/8] cgroup: convert cgroup_ida to cgroup_idr Li Zefan
2013-07-29 7:07 ` Li Zefan
2013-07-29 7:07 ` Li Zefan
[not found] ` <51F614C4.7060602-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2013-07-29 18:28 ` Tejun Heo
2013-07-29 18:28 ` Tejun Heo
2013-07-29 18:28 ` Tejun Heo
2013-07-30 1:10 ` Li Zefan
2013-07-30 1:10 ` Li Zefan
2013-07-30 14:21 ` Tejun Heo
2013-07-30 14:21 ` Tejun Heo
2013-07-29 7:09 ` [PATCH v3 6/8] memcg: fail to create cgroup if the cgroup id is too big Li Zefan
2013-07-29 7:09 ` Li Zefan
2013-07-29 7:09 ` Li Zefan
2013-07-29 7:09 ` [PATCH v3 7/8] memcg: stop using css id Li Zefan
2013-07-29 7:09 ` Li Zefan
2013-07-29 7:09 ` Li Zefan
2013-07-29 7:10 ` [PATCH v3 8/8] cgroup: kill css_id Li Zefan
2013-07-29 7:10 ` Li Zefan
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=51F711FE.3040006@huawei.com \
--to=lizefan-hv44wf8li93qt0dzr+alfa@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=glommer-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org \
--cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
--cc=kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=mhocko-AlSwsSmVLrQ@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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: link
Be 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.