[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091013051953.GA19895@x200>
Date: Tue, 13 Oct 2009 09:19:53 +0400
From: Alexey Dobriyan <adobriyan@...il.com>
To: Sukadev Bhattiprolu <sukadev@...ux.vnet.ibm.com>
Cc: linux-kernel@...r.kernel.org, Oren Laadan <orenl@...columbia.edu>,
serue@...ibm.com, "Eric W. Biederman" <ebiederm@...ssion.com>,
Pavel Emelyanov <xemul@...nvz.org>,
Andrew Morton <akpm@...l.org>, torvalds@...ux-foundation.org,
mikew@...gle.com, mingo@...e.hu, hpa@...or.com,
Nathan Lynch <nathanl@...tin.ibm.com>, arnd@...db.de,
peterz@...radead.org, Louis.Rilling@...labs.com, roland@...hat.com,
kosaki.motohiro@...fujitsu.com, randy.dunlap@...cle.com,
linux-api@...r.kernel.org,
Containers <containers@...ts.linux-foundation.org>,
sukadev@...ibm.com
Subject: Re: [RFC][v8][PATCH 3/10]: Make pid_max a pid_ns property
On Mon, Oct 12, 2009 at 09:50:41PM -0700, Sukadev Bhattiprolu wrote:
> From: Serge Hallyn <serue@...ibm.com>
> Subject: [RFC][v8][PATCH 3/10]: Make pid_max a pid_ns property
>
> Remove the pid_max global, and make it a property of the
> pid_namespace. When a pid_ns is created, it inherits
> the parent's pid_ns.
>
> Fixing up sysctl (trivial akin to ipc version, but
> potentially tedious to get right for all CONFIG*
> combinations) is left for later.
pid_max is not pid_ns property, it's just sysctl to limit cpu time
during bitmap search. Just like vm.max_map_count limits kernel memory
used by VMAs.
--
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