Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759819AbZJMNOH (ORCPT ); Tue, 13 Oct 2009 09:14:07 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759786AbZJMNOG (ORCPT ); Tue, 13 Oct 2009 09:14:06 -0400 Received: from mailhub.sw.ru ([195.214.232.25]:40112 "EHLO relay.sw.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759500AbZJMNOE (ORCPT ); Tue, 13 Oct 2009 09:14:04 -0400 Message-ID: <4AD47C1F.7040703@openvz.org> Date: Tue, 13 Oct 2009 17:09:51 +0400 From: Pavel Emelyanov User-Agent: Thunderbird 2.0.0.21 (X11/20090320) MIME-Version: 1.0 To: Sukadev Bhattiprolu CC: linux-kernel@vger.kernel.org, Oren Laadan , serue@us.ibm.com, "Eric W. Biederman" , Alexey Dobriyan , Pavel Emelyanov , Andrew Morton , torvalds@linux-foundation.org, mikew@google.com, mingo@elte.hu, hpa@zytor.com, Nathan Lynch , arnd@arndb.de, peterz@infradead.org, Louis.Rilling@kerlabs.com, roland@redhat.com, kosaki.motohiro@jp.fujitsu.com, randy.dunlap@oracle.com, linux-api@vger.kernel.org, Containers , sukadev@us.ibm.com Subject: Re: [RFC][v8][PATCH 3/10]: Make pid_max a pid_ns property References: <20091013044925.GA28181@us.ibm.com> <20091013045041.GC28435@us.ibm.com> In-Reply-To: <20091013045041.GC28435@us.ibm.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1125 Lines: 29 Sukadev Bhattiprolu wrote: > > From: Serge Hallyn > 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. > > Changelog[v2]: > - Port to newer kernel > - Make pid_max a local variable in alloc_pidmap() to simplify code/patch > > Signed-off-by: Serge Hallyn > Signed-off-by: Sukadev Bhattiprolu Not that I'm about to slow down or block the process, but... frankly I don't see the reason for doing so. Why should we? Especially taking into account, that we essentially cannot change thin in the namespace level 3 and deeper? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/