LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Oren Laadan <orenl@cs.columbia.edu>,
	linux-api@vger.kernel.org, containers@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	viro@zeniv.linux.org.uk, hpa@zytor.com, tglx@linutronix.de,
	torvalds@linux-foundation.org
Subject: Re: [RFC v7][PATCH 0/9] Kernel based checkpoint/restart
Date: Wed, 22 Oct 2008 11:20:24 +0200	[thread overview]
Message-ID: <20081022092024.GC12453@elte.hu> (raw)
In-Reply-To: <1224621667.1848.228.camel@nimitz>


* Dave Hansen <dave@linux.vnet.ibm.com> wrote:

> On Tue, 2008-10-21 at 12:21 -0700, Andrew Morton wrote:
> > 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).
> > 
> > - how useful is this code as it stands in real-world usage?
> 
> Right now, an application must be specifically written to use these 
> mew system calls.  It must be a single process and not share any 
> resources with other processes.  The only file descriptors that may be 
> open are simple files and may not include sockets or pipes.
> 
> What this means in practice is that it is useful for a simple app 
> doing computational work.

say a chemistry application doing calculations. Or a raytracer with a 
large job. Both can take many hours (days!) even on very fast machine 
and the restrictions on rebootability can hurt in such cases.

You should reach a minimal level of initial practical utility: say some 
helper tool that allows testers to checkpoint and restore a real PovRay 
session - without any modification to a stock distro PovRay.

	Ingo

  reply	other threads:[~2008-10-22  9:20 UTC|newest]

Thread overview: 35+ 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 ` [RFC v7][PATCH 0/9] Kernel based checkpoint/restart Andrew Morton
2008-10-21 20:41   ` Dave Hansen
2008-10-22  9:20     ` Ingo Molnar [this message]
2008-10-22 11:51       ` Daniel Lezcano

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=20081022092024.GC12453@elte.hu \
    --to=mingo@elte.hu \
    --cc=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=orenl@cs.columbia.edu \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    --subject='Re: [RFC v7][PATCH 0/9] Kernel based checkpoint/restart' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).