Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751283AbWBCRvc (ORCPT ); Fri, 3 Feb 2006 12:51:32 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751271AbWBCRvc (ORCPT ); Fri, 3 Feb 2006 12:51:32 -0500 Received: from smtp.osdl.org ([65.172.181.4]:23691 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S1751283AbWBCRvb (ORCPT ); Fri, 3 Feb 2006 12:51:31 -0500 Date: Fri, 3 Feb 2006 09:49:56 -0800 (PST) From: Linus Torvalds To: Kirill Korotaev cc: Kirill Korotaev , Andrew Morton , Linux Kernel Mailing List , frankeh@watson.ibm.com, clg@fr.ibm.com, haveblue@us.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 In-Reply-To: <43E3915A.2080000@sw.ru> Message-ID: References: <43E38BD1.4070707@openvz.org> <43E3915A.2080000@sw.ru> 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: 1784 Lines: 40 On Fri, 3 Feb 2006, Kirill Korotaev wrote: > > Do you have any other ideas/comments on this? > I will send additional IPC/filesystems virtualization patches a bit later. I think that a patch like this - particularly just the 1/5 part - makes total sense, because regardless of any other details of virtualization, every single scheme is going to need this. So I think at least 1/5 (and quite frankly, 2-3/5 look that way too) are things that we can (and probably should) merge quickly, so that people can then actually look at the differences in the places that they may actually disagree about. One thing I don't particularly like is some of the naming. To me "vps" doesn't sound particularly generic or logical. I realize that it probably makes perfect sense to you (and I assume it just means "virtual private servers"), but especially if you see patches 1-3 to really be independent of any "actual" virtualization code that is totally generic, I'd actually prefer a less specialized name. I realize that what things like this is used for is VPS web hosting etc, but that's really naming by current common usage, not by any real "logic". In other words, I personally would have called them "container" or something similar, rather than "vps_info". See? From a logical implementation standpoint, the fact that it is right now most commonly used for VPS hosting is totally irrelevant to the code, no? (And hey, maybe your "vps" means something different. In which case my argument makes even more sense ;) Linus - 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/