From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756978AbZB0QPW (ORCPT ); Fri, 27 Feb 2009 11:15:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752414AbZB0QPH (ORCPT ); Fri, 27 Feb 2009 11:15:07 -0500 Received: from e9.ny.us.ibm.com ([32.97.182.139]:43492 "EHLO e9.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752205AbZB0QPE (ORCPT ); Fri, 27 Feb 2009 11:15:04 -0500 Subject: Re: How much of a mess does OpenVZ make? ;) Was: What can OpenVZ do? From: Dave Hansen To: Alexey Dobriyan Cc: Ingo Molnar , linux-api@vger.kernel.org, containers@lists.linux-foundation.org, hpa@zytor.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, viro@zeniv.linux.org.uk, mpm@selenic.com, Andrew Morton , torvalds@linux-foundation.org, tglx@linutronix.de, xemul@openvz.org In-Reply-To: <20090226223112.GA2939@x200.localdomain> References: <1234285547.30155.6.camel@nimitz> <20090211141434.dfa1d079.akpm@linux-foundation.org> <1234462282.30155.171.camel@nimitz> <1234467035.3243.538.camel@calx> <20090212114207.e1c2de82.akpm@linux-foundation.org> <1234475483.30155.194.camel@nimitz> <20090212141014.2cd3d54d.akpm@linux-foundation.org> <1234479845.30155.220.camel@nimitz> <20090226162755.GB1456@x200.localdomain> <20090226173302.GB29439@elte.hu> <20090226223112.GA2939@x200.localdomain> Content-Type: text/plain Date: Fri, 27 Feb 2009 08:14:58 -0800 Message-Id: <1235751298.26788.372.camel@nimitz> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2009-02-27 at 01:31 +0300, Alexey Dobriyan wrote: > > I think the main question is: will we ever find ourselves in the > > future saying that "C/R sucks, nobody but a small minority uses > > it, wish we had never merged it"? I think the likelyhood of that > > is very low. I think the current OpenVZ stuff already looks very > > useful, and i dont think we've realized (let alone explored) all > > the possibilities yet. > > This is collecting and start of dumping part of cleaned up OpenVZ C/R > implementation, FYI. Are you just posting this to show how you expect c/r to look eventually? Or are you proposing this as an alternative to what Oren has bee posting? -- Dave