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: Tue, 7 May 2002 18:26:20 +0200 [thread overview]
Message-ID: <20020507182620.U2539@marowsky-bree.de> (raw)
In-Reply-To: <20020506181427.K918@marowsky-bree.de> <200205062055.PAA04067@ccure.karaya.com>
On 2002-05-06T15:55:52,
Jeff Dike <jdike@karaya.com> said:
> > but spreading an instance across multiple nodes is nowhere as simple
> > as it seems;
> It is if you want to be sufficiently stupid about it :-)
Ugh.
> > where do you keep OS data,
> It gets faulted from host to host as needed.
Ugh Ugh Ugh. You need coherency algorithms for these.
> > IO access,
> This scheme (and any clustering scheme, I think) would need back channels
> for one node to access the devices of another
Right. You need communication services and coherency algorithms for these ;-)
> > scheduling decisions,
> This machine thinks it's a normal SMP box, so scheduling happens as normal
Ugh ugh ugh. Too many page faults; you need a scheduler capable of keeping
node affinity.
> > inter-node communication in the first place, how to deal
> > with node failure etc...
> Maybe I'm not familiar enough with the clustering world, but I was under the
> impression that with a normal SSI cluster, the nodes are like CPUs in an
> SMP box - if one fails, the whole thing dies. In other words, that SSI
> clustering and HA clustering are pretty disjoint.
No. In the optimal case, nothing dies. ;-) In the less than optimal case, only
the processes affected directly by the failure die (the processes which had
dirty pages there etc).
In the really useless case, the entire cluster goes down like on a SMP box or
an unpartitioned CC-NUMA.
"In search of clusters" is definetely highly recommended reading. It is very
entertaining, too.
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-07 16:26 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
2002-05-06 20:55 ` Jeff Dike
2002-05-07 16:26 ` Lars Marowsky-Bree [this message]
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=20020507182620.U2539@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