From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751385AbWDHNpZ (ORCPT ); Sat, 8 Apr 2006 09:45:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751402AbWDHNpZ (ORCPT ); Sat, 8 Apr 2006 09:45:25 -0400 Received: from cantor.suse.de ([195.135.220.2]:59354 "EHLO mx1.suse.de") by vger.kernel.org with ESMTP id S1751385AbWDHNpX (ORCPT ); Sat, 8 Apr 2006 09:45:23 -0400 To: "Serge E. Hallyn" Cc: linux-kernel@vger.kernel.org Subject: Re: [RFC][PATCH 1/5] uts namespaces: Implement utsname namespaces References: <20060407095132.455784000@sergelap> <20060407183600.C8A8F19B8FD@sergelap.hallyn.com> From: Andi Kleen In-Reply-To: <20060407183600.C8A8F19B8FD@sergelap.hallyn.com> User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 Date: 08 Apr 2006 15:45:17 +0200 Message-ID: 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 "Serge E. Hallyn" writes: > This patch defines the uts namespace and some manipulators. > Adds the uts namespace to task_struct, and initializes a > system-wide init namespace which will continue to be used when > it makes sense. So to get this straight - you want to add a new pointer to task_struct for each possible virtualized entity? After you're doing by how many bytes will task_struct be bloated? I don't think that's a very good approach because you'll crank up the per thread memory overhead which is already far too big in Linux. Also it adds cache foot print and generally makes things slower. If anything I would request using a proxy data structure that contains all the virtualized namespaces for a set of processes. And give each task only has a single pointer to one of these. -Andi