From: Andrew Morton <akpm@linux-foundation.org>
To: Oren Laadan <orenl@cs.columbia.edu>
Cc: torvalds@linux-foundation.org,
containers@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-api@vger.kernel.org, tglx@linutronix.de, serue@us.ibm.com,
dave@linux.vnet.ibm.com, mingo@elte.hu, hpa@zytor.com,
viro@zeniv.linux.org.uk
Subject: Re: [RFC v7][PATCH 0/9] Kernel based checkpoint/restart
Date: Tue, 21 Oct 2008 12:21:35 -0700 [thread overview]
Message-ID: <20081021122135.4bce362c.akpm@linux-foundation.org> (raw)
In-Reply-To: <1224481237-4892-1-git-send-email-orenl@cs.columbia.edu>
On Mon, 20 Oct 2008 01:40:28 -0400
Oren Laadan <orenl@cs.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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-10-21 19:21 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 5:40 Oren Laadan
2008-10-20 5:40 ` [RFC v7][PATCH 1/9] Create syscalls: sys_checkpoint, sys_restart Oren Laadan
2008-10-20 5:40 ` [RFC v7][PATCH 2/9] General infrastructure for checkpoint restart Oren Laadan
2008-10-21 19:41 ` Andrew Morton
2008-10-21 20:24 ` Serge E. Hallyn
2008-10-21 20:41 ` Andrew Morton
2008-10-22 1:33 ` Oren Laadan
2008-10-22 2:55 ` Daniel Jacobowitz
2008-10-22 3:02 ` Dave Hansen
2008-10-22 14:29 ` Daniel Jacobowitz
2008-10-22 15:28 ` Serge E. Hallyn
2008-10-22 16:02 ` Oren Laadan
2008-10-22 17:03 ` Serge E. Hallyn
2008-10-22 18:32 ` Oren Laadan
2008-10-27 8:27 ` Peter Chubb
2008-10-27 11:03 ` Oren Laadan
2008-10-27 16:42 ` Dave Hansen
2008-10-27 17:11 ` Oren Laadan
2008-10-27 20:51 ` Matt Helsley
2008-10-27 21:20 ` Serge E. Hallyn
2008-10-27 21:51 ` Oren Laadan
2008-10-27 22:09 ` Dave Hansen
2008-10-28 18:33 ` Serge E. Hallyn
2008-10-20 5:40 ` [RFC v7][PATCH 3/9] x86 support for checkpoint/restart Oren Laadan
2008-10-20 5:40 ` [RFC v7][PATCH 4/9] Dump memory address space Oren Laadan
2008-10-20 5:40 ` [RFC v7][PATCH 5/9] Restore " Oren Laadan
2008-10-20 5:40 ` [RFC v7][PATCH 6/9] Checkpoint/restart: initial documentation Oren Laadan
2008-10-28 16:48 ` Michael Kerrisk
2008-10-20 5:40 ` [RFC v7][PATCH 7/9] Infrastructure for shared objects Oren Laadan
2008-10-20 5:40 ` [RFC v7][PATCH 8/9] Dump open file descriptors Oren Laadan
2008-10-20 5:40 ` [RFC v7][PATCH 9/9] Restore open file descriprtors Oren Laadan
2008-10-21 19:21 ` Andrew Morton [this message]
2008-10-21 20:41 ` [RFC v7][PATCH 0/9] Kernel based checkpoint/restart Dave Hansen
2008-10-22 9:20 ` Ingo Molnar
2008-10-22 11:51 ` Daniel Lezcano
2008-10-22 11:55 ` Cedric Le Goater
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081021122135.4bce362c.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=hpa@zytor.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=orenl@cs.columbia.edu \
--cc=serue@us.ibm.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox