[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130724140751.GE2540@dhcp22.suse.cz>
Date: Wed, 24 Jul 2013 16:07:51 +0200
From: Michal Hocko <mhocko@...e.cz>
To: Li Zefan <lizefan@...wei.com>
Cc: Tejun Heo <tj@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Glauber Costa <glommer@...allels.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
Johannes Weiner <hannes@...xchg.org>,
LKML <linux-kernel@...r.kernel.org>,
Cgroups <cgroups@...r.kernel.org>, linux-mm@...ck.org
Subject: Re: [PATCH v2 2/8] cgroup: document how cgroup IDs are assigned
On Wed 24-07-13 17:59:55, 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 an array.
>
> Signed-off-by: Li Zefan <lizefan@...ei.com>
Reviewed-by: Michal Hocko <mhocko@...e.cz>
> ---
> include/linux/cgroup.h | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/include/linux/cgroup.h b/include/linux/cgroup.h
> index 2bd052d..8c107e9 100644
> --- a/include/linux/cgroup.h
> +++ b/include/linux/cgroup.h
> @@ -161,7 +161,13 @@ struct cgroup_name {
> struct cgroup {
> unsigned long flags; /* "unsigned long" so bitops work */
>
> - int id; /* idr allocated in-hierarchy ID */
> + /*
> + * idr allocated in-hierarchy ID.
> + *
> + * The ID of the root cgroup is always 0, and a new cgroup
> + * will be assigned with a smallest available ID.
> + */
> + int id;
>
> /*
> * We link our 'sibling' struct into our parent's 'children'.
> --
> 1.8.0.2
>
> --
> To unsubscribe from this list: send the line "unsubscribe cgroups" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Michal Hocko
SUSE Labs
--
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