[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101117153902.GA1155@hallyn.com>
Date: Wed, 17 Nov 2010 09:39:02 -0600
From: "Serge E. Hallyn" <serge@...lyn.com>
To: Tejun Heo <tj@...nel.org>
Cc: Oren Laadan <orenl@...columbia.edu>,
Kapil Arya <kapil@....neu.edu>,
Gene Cooperman <gene@....neu.edu>,
linux-kernel@...r.kernel.org, Matt Helsley <matthltc@...ibm.com>,
Linux Containers <containers@...ts.osdl.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>, xemul@...ru
Subject: Re: [Ksummit-2010-discuss] checkpoint-restart: naked patch
Quoting Tejun Heo (tj@...nel.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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists