From: Lars Marowsky-Bree <lmb@suse.de>
To: Jeff Dike <jdike@karaya.com>
Cc: linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net,
user-mode-linux-user@lists.sourceforge.net
Subject: Re: [uml-devel] Re: UML is now self-hosting!
Date: Mon, 6 May 2002 18:14:27 +0200 [thread overview]
Message-ID: <20020506181427.K918@marowsky-bree.de> (raw)
In-Reply-To: <20020505082505.GE2392@matchmail.com> <200205051225.HAA01629@ccure.karaya.com>
On 2002-05-05T07:25:00,
Jeff Dike <jdike@karaya.com> said:
> MOSIX (or Compaq's SSI) would certainly be a way of doing it. It happens
> that there's a particularly simple way of doing it with UML. You'd partition
> UML's 'physical' memory between the hosts, and use the fact that those pages
> are really virtual to fault them between hosts as needed. This would perform
> particularly badly, but its simplicity appeals to me.
An interesting and simple approach indeed; but spreading an instance across
multiple nodes is nowhere as simple as it seems; where do you keep OS data, IO
access, scheduling decisions, inter-node communication in the first place, how
to deal with node failure etc...
However, I believe it could potentially be implemented cleaner than currently
with the Compaq SSI stuff, because the encapsulation is better etc; but I have
been known to be wrong ;-)
It would certainly be very interesting. If you _really_ want to open this can
of worms, you should consider joining linux-cluster mailing list for this, or
the Open Clustering Framework list (because you are going to stumble into the
madness which is "interoperability and lack of standards" here).
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
Immortality is an adequate definition of high availability for me.
--- Gregory F. Pfister
next prev parent reply other threads:[~2002-05-06 16:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-03 21:08 UML is now self-hosting! Jeff Dike
2002-05-03 22:24 ` Jeff Dike
2002-05-03 21:51 ` Guest section DW
2002-05-03 22:28 ` Gerrit Huizenga
2002-05-04 6:28 ` Christoph Hellwig
2002-05-04 17:12 ` Gerrit Huizenga
2002-05-04 1:32 ` Jeff Dike
2002-04-27 1:22 ` Pavel Machek
2002-05-06 16:57 ` Jeff Dike
2002-05-05 8:25 ` Mike Fedyk
2002-05-05 8:29 ` Vikram
2002-05-05 8:42 ` Mike Fedyk
2002-05-05 12:25 ` Jeff Dike
2002-05-05 16:21 ` Larry McVoy
2002-05-06 0:06 ` [uml-devel] " Jeff Dike
2002-05-06 16:14 ` Lars Marowsky-Bree [this message]
2002-05-06 20:55 ` Jeff Dike
2002-05-07 16:26 ` Lars Marowsky-Bree
2002-05-07 13:29 ` Rob Landley
2002-05-07 19:35 ` Jeff Dike
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=20020506181427.K918@marowsky-bree.de \
--to=lmb@suse.de \
--cc=jdike@karaya.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@lists.sourceforge.net \
/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