All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wilfried Weissmann <Wilfried.Weissmann@gmx.at>
To: Torrey Hoffman <torrey.hoffman@myrio.com>
Cc: "'jesse@cats-chateau.net'" <jesse@cats-chateau.net>,
	Kip Macy <kmacy@netapp.com>, Paul Jakma <paul@clubi.ie>,
	Helge Hafting <helgehaf@idb.hist.no>,
	"C. Slater" <cslater@wcnet.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Switching Kernels without Rebooting?
Date: Thu, 12 Jul 2001 22:47:00 +0200	[thread overview]
Message-ID: <3B4E0CC4.1926053C@gmx.at> (raw)
In-Reply-To: <D52B19A7284D32459CF20D579C4B0C0211C92A@mail0.myrio.com>

Torrey Hoffman wrote:
> 
> Jesse Pollard wrote:
> 
> [why switching kernels is very hard, and...]
> 
> > Before you even try switching kernels, first implement a process
> > checkpoint/restart. The process must be resumed after a boot
> > using the same
> > kernel, with all I/O resumed. Now get it accepted into the kernel.
> 
> Hear, hear!  That would be a useful feature, maybe not network servers,
> but for pure number crunching apps it would save people having to write
> all the state saving and recovery that is needed now for long term
> computations.

There is a checkpointing and resumeing lib at
ftp://gutemine.geo.uni-koeln.de/pub/chkpt/
I am not sure if it has been ported to linux yet, but it might be worth
a look.

> 
> For bonus points, make it work for clusters to synchronously save and
> restore state for the apps running on all the nodes at once...
> 
> Torrey

bye,
Wilfried

  parent reply	other threads:[~2001-07-12 20:45 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-12  1:03 Switching Kernels without Rebooting? Torrey Hoffman
2001-07-12  1:24 ` C. Slater
2001-07-12 10:07   ` Jesse Pollard
2001-07-12 12:11     ` Ian Stirling
2001-07-12 12:54       ` Jesse Pollard
2001-07-12 14:15         ` Michael H. Warfield
2001-07-12 23:21           ` swsusp [was Re: Switching Kernels without Rebooting?] Pavel Machek
2001-07-12 23:17   ` Switching Kernels without Rebooting? Pavel Machek
2001-07-12 20:47 ` Wilfried Weissmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-13  1:11 tas
2001-07-13  3:45 ` Ian Stirling
2001-07-12 15:32 Jesse Pollard
2001-07-12 12:23 Jesse Pollard
2001-07-12 14:55 ` Ralf Baechle
2001-07-12  4:48 Frank Davis
2001-07-12  5:08 ` John Alvord
2001-07-13  9:10   ` Chuck Hemker
     [not found] <994895240.21189@whiskey.enposte.net>
2001-07-12  0:10 ` Stuart Lynne
2001-07-11  9:52 David Balazic
2001-07-11 10:08 ` Laramie Leavitt
2001-07-11 19:12   ` H. Peter Anvin
2001-07-11 15:19 ` C. Slater
     [not found] <NOEJJDACGOHCKNCOGFOMOEKECGAA.davids@webmaster.com>
2001-07-10 20:43 ` C. Slater
2001-07-11  3:50   ` FORT David
2001-07-11  9:10   ` Helge Hafting
2001-07-11 15:41     ` C. Slater
2001-07-12 10:16       ` Helge Hafting
2001-07-11 22:12     ` Paul Jakma
2001-07-11 22:14       ` Rik van Riel
2001-07-11 22:36         ` C. Slater
2001-07-11 23:44           ` Andreas Dilger
2001-07-12  1:17             ` C. Slater
2001-07-12 15:39               ` Rik van Riel
2001-07-12 16:23                 ` Albert D. Cahalan
2001-07-12 17:37                   ` Mike Borrelli
2001-07-12 18:05                   ` Rik van Riel
2001-07-13 10:07                     ` Pau Aliagas
2001-07-12 18:48                   ` Chris Friesen
2001-07-12 10:12             ` Ralf Baechle
2001-07-12 15:32           ` Rik van Riel
2001-07-11 22:36         ` David Schwartz
2001-07-12  7:23         ` Kai Henningsen
2001-07-12 10:05           ` Helge Hafting
2001-07-13  6:50             ` Kai Henningsen
2001-07-12 17:58           ` Hua Zhong
2001-07-11 22:46       ` Kip Macy
2001-07-11 23:02         ` Rik van Riel
2001-07-12  0:31         ` Jesse Pollard
2001-07-12  1:10           ` Hua Zhong
2001-07-11 23:36       ` H. Peter Anvin
2001-07-12  7:23       ` Ville Herva
2001-07-10 18:42 C. Slater
2001-07-10 18:50 ` Chris Wedgwood
2001-07-10 21:11 ` Jesper Juhl

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=3B4E0CC4.1926053C@gmx.at \
    --to=wilfried.weissmann@gmx.at \
    --cc=cslater@wcnet.org \
    --cc=helgehaf@idb.hist.no \
    --cc=jesse@cats-chateau.net \
    --cc=kmacy@netapp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@clubi.ie \
    --cc=torrey.hoffman@myrio.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.