[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20081021122135.4bce362c.akpm@linux-foundation.org>
Date: Tue, 21 Oct 2008 12:21:35 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Oren Laadan <orenl@...columbia.edu>
Cc: torvalds@...ux-foundation.org,
containers@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-api@...r.kernel.org, tglx@...utronix.de, serue@...ibm.com,
dave@...ux.vnet.ibm.com, mingo@...e.hu, hpa@...or.com,
viro@...iv.linux.org.uk, orenl@...columbia.edu
Subject: Re: [RFC v7][PATCH 0/9] Kernel based checkpoint/restart
On Mon, 20 Oct 2008 01:40:28 -0400
Oren Laadan <orenl@...columbia.edu> wrote:
> These patches implement basic checkpoint-restart [CR]. This version
> (v7) supports basic tasks with simple private memory, and open files
> (regular files and directories only).
This is a problem. I wouldn't want to be in a position where we merge
this code in mainline, but it's just a not-very-useful toy. Then, as
we turn it into a useful non-toy it all turns into an utter mess.
IOW, merging this code as-is will commit us to merging more code which
hasn't even been written yet. It might even commit us to solving
thus-far-unknown problems which we don't know how to solve!
It's a big blank cheque.
So.
- how useful is this code as it stands in real-world usage?
- what additional work needs to be done to it? (important!)
- how far are we down the design and implementation path with that new
work? Are we yet at least in a position where we can say "yes, this
feature can be completed and no, it won't be a horrid mess"?
--
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