From: ebiederm@xmission.com (Eric W. Biederman)
To: Steven Cole <elenstev@mesatop.com>
Cc: linux-kernel@vger.kernel.org, Larry McVoy <lm@bitmover.com>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: Kernel hot-swap using Kexec, BProc and CC/SMP Clusters.
Date: 05 May 2003 11:34:24 -0600 [thread overview]
Message-ID: <m1d6ixb8m7.fsf@frodo.biederman.org> (raw)
In-Reply-To: <1052140733.2163.93.camel@spc9.esa.lanl.gov>
So summarize:
1) Run multiple kernels (minimally kernels A and B)
2) Migrate processes from kernel A to kernel B
3) Use kexec to replace kernel A once all processes have left.
4) Repeat for all other kernels.
On two simple machines working in tandem (The most common variation
used for high availability this should be easy to do). And it is
preferable to a reboot because of the additional control and speed.
Thank you for the perspective. This looks like I line I can
sell to get some official time to work on kexec and it's friends
more actively.
>From what I have seen process migration/process check-pointing is
currently the very rough area.
The interesting thing becomes how do you measure system uptime.
Eric
next prev parent reply other threads:[~2003-05-05 17:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 13:18 Kernel hot-swap using Kexec, BProc and CC/SMP Clusters Steven Cole
2003-05-05 14:22 ` Karim Yaghmour
2003-05-05 17:34 ` Eric W. Biederman [this message]
2003-05-05 18:00 ` Steven Cole
2003-05-05 18:17 ` Valdis.Kletnieks
2003-05-05 19:51 ` Steven Cole
2003-05-05 20:25 ` Richard B. Johnson
2003-05-05 18:16 ` Chris Friesen
2003-05-06 1:28 ` Steven Cole
-- strict thread matches above, loose matches on Subject: below --
2003-05-06 3:19 Stephen M. Kenton
2003-05-06 9:49 ` Eric W. Biederman
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=m1d6ixb8m7.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=elenstev@mesatop.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox