Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758425Ab0KQPjG (ORCPT ); Wed, 17 Nov 2010 10:39:06 -0500 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.125]:56267 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758210Ab0KQPjE (ORCPT ); Wed, 17 Nov 2010 10:39:04 -0500 X-Authority-Analysis: v=1.1 cv=NFUeGz0loTdi/T6hXKngYYtckjed7x3pKvNOqmBBK18= c=1 sm=0 a=f8wm_IhKjn4A:10 a=kj9zAlcOel0A:10 a=ClVPYAY4FByjUdLuiT8neg==:17 a=VwQbUJbxAAAA:8 a=6rqHouBjAAAA:8 a=OsuJWyxC5J6dQxHz35kA:9 a=1muazlLnOKmt72RTAOmti-c3HzIA:4 a=CjuIK1q_8ugA:10 a=LI9Vle30uBYA:10 a=ClVPYAY4FByjUdLuiT8neg==:117 X-Cloudmark-Score: 0 X-Originating-IP: 66.68.83.102 Date: Wed, 17 Nov 2010 09:39:02 -0600 From: "Serge E. Hallyn" To: Tejun Heo Cc: Oren Laadan , Kapil Arya , Gene Cooperman , linux-kernel@vger.kernel.org, Matt Helsley , Linux Containers , "Eric W. Biederman" , xemul@sw.ru Subject: Re: [Ksummit-2010-discuss] checkpoint-restart: naked patch Message-ID: <20101117153902.GA1155@hallyn.com> References: <4CD26948.7050009@kernel.org> <20101104164401.GC10656@sundance.ccs.neu.edu> <4CD3CE29.2010105@kernel.org> <20101106053204.GB12449@count0.beaverton.ibm.com> <20101106204008.GA31077@sundance.ccs.neu.edu> <4CD5D99A.8000402@cs.columbia.edu> <20101107184927.GF31077@sundance.ccs.neu.edu> <4CD72150.9070705@cs.columbia.edu> <4CE3C334.9080401@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4CE3C334.9080401@kernel.org> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1264 Lines: 27 Quoting Tejun Heo (tj@kernel.org): > Hello, Oren. > > On 11/07/2010 10:59 PM, Oren Laadan wrote: > > We could work to add ABIs and APIs for each and every possible piece > > of state that affects userspace. And for each we'll argue forever > > about the design and some time later regret that it wasn't designed > > correctly :p > > I'm sorry but in-kernel CR already looks like a major misdesign to me. By this do you mean the very idea of having CR support in the kernel? Or our design of it in the kernel? Let's go back to July 2008, at the containers mini-summit, where it was unanimously agreed upon that the kernel was the right place (Checkpoint/Resetart [CR] under http://wiki.openvz.org/Containers/Mini-summit_2008_notes ), and that we would start by supporting a single task with no resources. Was that whole discussion effectively misguided, in your opinion? Or do you feel that since the first steps outlined in that discussion we've either "gone too far" or strayed in the subsequent design? -serge -- 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/