[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <m1ocs0dd52.fsf@fess.ebiederm.org>
Date: Sat, 04 Jul 2009 02:13:29 -0700
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Paul Menage <menage@...gle.com>
Cc: "Serge E. Hallyn" <serue@...ibm.com>,
Li Zefan <lizf@...fujitsu.com>,
Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Linux Containers <containers@...ts.linux-foundation.org>
Subject: Re: [PATCH][BUGFIX] cgroups: fix pid namespace bug
Paul Menage <menage@...gle.com> writes:
> On Thu, Jul 2, 2009 at 6:26 AM, Serge E. Hallyn<serue@...ibm.com> wrote:
>> Quoting Li Zefan (lizf@...fujitsu.com):
>>> Paul Menage wrote:
>>> > On Wed, Jul 1, 2009 at 7:17 PM, Li Zefan<lizf@...fujitsu.com> wrote:
>>> >> But I guess we are going to fix the bug for 2.6.31? So is it ok to
>>> >> merge a new feature 'cgroup.procs' together into 2.6.31?
>>> >>
>>> >
>>> > Does this bug really need to be fixed for 2.6.31? I didn't think that
>>> > the namespace support in mainline was robust enough yet for people to
>>> > use them for virtual servers in production environments.
>>
>> I don't know where the bar is for 'production environments', but I'd
>> have to claim that pid namespaces are there...
>
> Well, pid namespaces are marked as experimental, as are user
> namespaces (and were described as "very incomplete" a few months
> back). Pid namespaces are useful for process migration (which is still
> under development) or virtual servers (for which user namespaces are
> pretty much essential). So I'm not sure quite what you'd use pid
> namespaces for yet.
I have pid namespaces in pretty heavy use already.
Inescapable process groups are quite handy.
Eric
--
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