From: "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: Switching Kernels without Rebooting? [MOSIX]
Date: Wed, 11 Jul 2001 14:11:56 -0400 [thread overview]
Message-ID: <20010711141156.B32049@megatonmonkey.net> (raw)
In-Reply-To: <NOEJJDACGOHCKNCOGFOMOEKECGAA.davids@webmaster.com> <001501c10980$f42035a0$fe00000a@cslater> <3B4C180E.D3AE1960@idb.hist.no> <005f01c10a20$03baf5a0$fe00000a@cslater>
In-Reply-To: <005f01c10a20$03baf5a0$fe00000a@cslater>; from cslater@wcnet.org on Wed, Jul 11, 2001 at 11:41:54AM -0400
On Wed, Jul 11, 2001 at 11:41:54AM -0400, C. Slater wrote:
> Unless we find some other way to do it, i think we will have to limit this
> to only switching between kernels with the same minor version. We probably
> would not beable to swap between 2.4 and 2.6 anyways, though it depends on
> what changes are made.
>
> Colin
Just thinking...
If you had enough money, and were inclined enough, one could setup the
following system:
- 2 Boxes, Running MOSIX (similar processors).
a. Start processes on Box 1.
b. Migrate processes to Box 2.
If the need to upgrade the kernel arises, you can migrate the processes
back to Box 1. Upgrade the kenrel on Box 2, recompile MOSIX.
If the first two digits of the MOSIX version are the same, you can migrate
the processes back to Box 2 (now running the latest kernel).
The stubs inplace for your process will run local kernel functions that
are not specifically host dependant, thus taking advantage of the newer
kernel features, and possibly newer hardware on Box 2, at an application
level.
Obviously, Box 1 could be smaller and less expensive.
Take note that if Box 1 were to fail, you process would die, since the
kernel stubs need to be in place on the original machine.
There are many cons to this system, but I will not ruin the decidely
happy mood of this linux-future-istic conversation ;)
Cheers,
Carlos O'Donell Jr.
-------------------------
Baldric Project
http://www.baldric.uwo.ca
-------------------------
next prev parent reply other threads:[~2001-07-11 18:12 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <NOEJJDACGOHCKNCOGFOMOEKECGAA.davids@webmaster.com>
2001-07-10 20:43 ` Switching Kernels without Rebooting? 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-11 18:11 ` Carlos O'Donell Jr. [this message]
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-12 23:24 ` swsusp again [was Re: Switching Kernels without Rebooting?] Pavel Machek
2001-07-13 21:08 ` Alan Cox
2001-07-11 22:46 ` Switching Kernels without Rebooting? 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
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=20010711141156.B32049@megatonmonkey.net \
--to=carlos@baldric.uwo.ca \
--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