[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090705063850.GX11273@balbir.in.ibm.com>
Date: Sun, 5 Jul 2009 12:08:50 +0530
From: Balbir Singh <balbir@...ux.vnet.ibm.com>
To: Paul Menage <menage@...gle.com>
Cc: lizf@...fujitzu.com, serue@...ibm.com, akpm@...ux-foundation.org,
containers@...ts.linux-foundation.org, bblum@...gle.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] CGroups: cgroup member list enhancement/fix
* menage@...gle.com <menage@...gle.com> [2009-07-02 16:26:15]:
> The following series (written by Ben Blum) adds a "cgroup.procs" file
> to each cgroup that reports unique tgids rather than pids, and fixes a
> pid namespace bug in the existing "tasks" file that could cause
> readers in different namespaces to interfere with one another.
>
> The patches as a pair provide similar functionality to Li Zefan's
> patch posted yesterday, with the addition on the "cgroup.procs" file;
> if it's decided that Li's patch needs to be fast-tracked to 2.6.31,
> then these patches can be rebased as a small extension of Li's patch;
> if Li'z patch doesn't need to go to 2.6.31 then it makes more sense to
> take this pair since they provide more overall functionality.
>
Paul, I don't see an interface to migrate all procs or at-least I
can't read it in the changelog. As discussed in the containers
mini-summit in 2008, it would be a nice thing to have (I've not looked
at the implementation yet).
> ---
>
> Ben Blum (2):
> Adds a read-only "procs" file similar to "tasks" that shows only unique tgids
> Ensures correct concurrent opening/reading of pidlists across pid namespaces
>
>
> include/linux/cgroup.h | 46 +++++-
> kernel/cgroup.c | 355 +++++++++++++++++++++++++++++++++---------------
> 2 files changed, 285 insertions(+), 116 deletions(-)
>
> _______________________________________________
> Containers mailing list
> Containers@...ts.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/containers
--
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