From: Neal Becker <ndbecker2@verizon.net>
To: linux-kernel@vger.kernel.org
Subject: Re: State of linux checkpointing?
Date: Wed, 28 Apr 2004 21:24:55 -0400 [thread overview]
Message-ID: <c6plh7$sqj$1@sea.gmane.org> (raw)
In-Reply-To: slrn-0.9.7.4-11992-4650-200404290913-tc@hexane.ssi.swin.edu.au
Tim Connors wrote:
> Jeff Garzik <jgarzik@pobox.com> said on Wed, 28 Apr 2004 16:23:00 -0400:
>> Neal D. Becker wrote:
>> > I wonder if there is a checkpointing that will work with 2.6 kernels?
>> >
>> > I only need relatively basic checkpointing. No sockets or fancy stuff.
>>
>> You only need checkpointing when your application programmers are lazy
>> and don't care about data integrity. :)
>
> Or you are running some kind of cluster where you want the
> applications to be checkpointed transparently without the application
> knowing the details of how or when they will be swapped out (but this
> will need sockets anyway, so won't happen anytime soon).
>
I want checkpointing for:
1) Protect against job interruption due to system crash, operator error,
power loss, whatever
2) Job mygration. Even manual job mygration would be nice.
next prev parent reply other threads:[~2004-04-29 1:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-28 17:15 State of linux checkpointing? Neal D. Becker
2004-04-28 20:23 ` Jeff Garzik
2004-04-28 23:17 ` Tim Connors
2004-04-29 1:24 ` Neal Becker [this message]
2004-04-29 16:31 ` Thomas Davis
2004-04-29 17:12 ` Tim Connors
2004-04-29 19:50 ` Neal D. Becker
[not found] <1Q3nZ-2hv-3@gated-at.bofh.it>
[not found] ` <1Q40J-2Mx-9@gated-at.bofh.it>
[not found] ` <1Q6F8-53t-1@gated-at.bofh.it>
[not found] ` <1Q8xl-6x2-17@gated-at.bofh.it>
2004-04-29 9:42 ` Ihar 'Philips' Filipau
-- strict thread matches above, loose matches on Subject: below --
2004-05-10 16:23 Nur Hussein
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='c6plh7$sqj$1@sea.gmane.org' \
--to=ndbecker2@verizon.net \
--cc=linux-kernel@vger.kernel.org \
/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