Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750820AbWCXVQd (ORCPT ); Fri, 24 Mar 2006 16:16:33 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751416AbWCXVQd (ORCPT ); Fri, 24 Mar 2006 16:16:33 -0500 Received: from ebiederm.dsl.xmission.com ([166.70.28.69]:46553 "EHLO ebiederm.dsl.xmission.com") by vger.kernel.org with ESMTP id S1750820AbWCXVQc (ORCPT ); Fri, 24 Mar 2006 16:16:32 -0500 To: Herbert Poetzl Cc: Kirill Korotaev , Dave Hansen , Sam Vilain , linux-kernel@vger.kernel.org, OpenVZ developers list , "Serge E.Hallyn" , Andrew Morton Subject: Re: [RFC] [PATCH 0/7] Some basic vserver infrastructure References: <20060321061333.27638.63963.stgit@localhost.localdomain> <1142967011.10906.185.camel@localhost.localdomain> <44241224.9000200@sw.ru> <20060324210150.GA22308@MAIL.13thfloor.at> From: ebiederm@xmission.com (Eric W. Biederman) Date: Fri, 24 Mar 2006 14:13:40 -0700 In-Reply-To: <20060324210150.GA22308@MAIL.13thfloor.at> (Herbert Poetzl's message of "Fri, 24 Mar 2006 22:01:50 +0100") Message-ID: User-Agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1181 Lines: 33 Herbert Poetzl writes: > hmm, isn't per process a little extreme ... I know > what you want to accomplish but won't this lead to > a per process procfs? Where all of the values vary per process possibly, that is they way /proc is supposed to be. /proc/sys is the only case that I think really gets extreme. For things like /proc/sysvipc and /proc/net it really is a natural break, and /proc/mounts already shows that the technique works fine. So I am trying to turn an ugly design choice into feature :) > and, if you want to do per > process procfs, what would be the gain? > > just my opinion ... Under the covers the implementation is per namespace, but it isn't easy to export it that way from procfs. In any event this appears to be a way to implement these things while retaining backwards compatibility, with the current implementation, and it looks like it can be implemented fairly cleanly. Eric - 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/