Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965051AbWBGMTk (ORCPT ); Tue, 7 Feb 2006 07:19:40 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965055AbWBGMTk (ORCPT ); Tue, 7 Feb 2006 07:19:40 -0500 Received: from mailhub.sw.ru ([195.214.233.200]:32091 "EHLO relay.sw.ru") by vger.kernel.org with ESMTP id S965051AbWBGMTj (ORCPT ); Tue, 7 Feb 2006 07:19:39 -0500 Message-ID: <43E890CB.1060608@sw.ru> Date: Tue, 07 Feb 2006 15:21:31 +0300 From: Kirill Korotaev User-Agent: Mozilla/5.0 (X11; U; Linux i686; ru-RU; rv:1.2.1) Gecko/20030426 X-Accept-Language: ru-ru, en MIME-Version: 1.0 To: Sam Vilain CC: Linus Torvalds , Dave Hansen , Kirill Korotaev , Andrew Morton , Linux Kernel Mailing List , frankeh@watson.ibm.com, clg@fr.ibm.com, greg@kroah.com, alan@lxorguk.ukuu.org.uk, serue@us.ibm.com, arjan@infradead.org, Rik van Riel , Alexey Kuznetsov , Andrey Savochkin , devel@openvz.org, Pavel Emelianov Subject: Re: [RFC][PATCH 1/5] Virtualization/containers: startup References: <43E38BD1.4070707@openvz.org> <43E3915A.2080000@sw.ru> <1138991641.6189.37.camel@localhost.localdomain> <43E61448.7010704@sw.ru> <43E7E998.2020007@vilain.net> In-Reply-To: <43E7E998.2020007@vilain.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1075 Lines: 27 >> So if some people don't like "container", how about just calling it >> "context"? The downside of that name is that it's very commonly used >> in the kenel, because a lot of things have "contexts". That's why >> "container" would be a lot better. >> >> I'd suggest >> >> current->container - the current EFFECTIVE container >> current->master_container - the "long term" container. >> >> (replace "master" with some other non-S&M term if you want) > > > Hmm. You actually need a linked list, otherwise you have replaced a one > level flat structure with a two level one, and you miss out on some of > the applications. VServer uses a special structure for this. Nope! :) This is pointer to current/effective container, which can be anywhere in the hierarchy. list should be inside container struct. Kirill - 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/