public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jakob Østergaard" <jakob@unthought.net>
To: Ben Ford <ben@kalifornia.com>
Cc: "Dwayne C. Litzenberger" <dlitz@dlitz.net>,
	Anton Blanchard <anton@samba.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CPU hot swap for 2.4.3 + s390 support
Date: Mon, 7 May 2001 03:42:08 +0200	[thread overview]
Message-ID: <20010507034208.A16593@unthought.net> (raw)
In-Reply-To: <20010505063726.A32232@va.samba.org> <20010506011553.A11297@zed.dlitz.net> <3AF584A2.4050208@kalifornia.com>
In-Reply-To: <3AF584A2.4050208@kalifornia.com>; from ben@kalifornia.com on Sun, May 06, 2001 at 10:06:42AM -0700

On Sun, May 06, 2001 at 10:06:42AM -0700, Ben Ford wrote:
> Dwayne C. Litzenberger wrote:
> 
> >Hey, this is cool.
> >
> >How far away is the capability to "teleport" processes from one machine to
> >another over the network?  Think of the uptime!
> >
> 
> It is here.  Look at Mosix.

No.  Not for uptime.

The "responsibility" for process completion does not get delegated. A process
will always be bound to it's home-node (in mosix terms), no matter how far
it's "teleported".   If the home-node fails, the process won't know what hit
it.

There are good reasons why mosix let's processes depend on their home nodes.

This is not meant as backstabbing mosix, it's a great environment for a lot
of things.

But it's not the universal silver bullet.

-- 
................................................................
:   jakob@unthought.net   : And I see the elder races,         :
:.........................: putrid forms of man                :
:   Jakob Østergaard      : See him rise and claim the earth,  :
:        OZ9ABN           : his downfall is at hand.           :
:.........................:............{Konkhra}...............:

  reply	other threads:[~2001-05-07  1:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-05 13:37 [PATCH] CPU hot swap for 2.4.3 + s390 support Anton Blanchard
2001-05-05 14:43 ` Peter Rival
2001-05-05 15:37   ` Chris Wedgwood
2001-05-05 16:34     ` Mitch Adair
2001-05-06  1:53       ` Chris Wedgwood
2001-05-06  2:24         ` Rik van Riel
2001-05-06  2:19       ` Rik van Riel
2001-05-06  0:08     ` Peter Rival
2001-05-06  2:02       ` Chris Wedgwood
2001-05-06  2:19     ` Rik van Riel
2001-05-06  2:25       ` Chris Wedgwood
2001-05-06  2:31         ` Rik van Riel
2001-05-06 15:38       ` David Woodhouse
2001-05-06  8:03   ` Aaron Lehmann
2001-05-06  8:43     ` Stephen Beynon
2001-05-06  7:15 ` Dwayne C. Litzenberger
2001-05-06  8:04   ` Aaron Lehmann
2001-05-06 17:06   ` Ben Ford
2001-05-07  1:42     ` Jakob Østergaard [this message]
2001-05-05 20:49       ` Bruce Harada

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=20010507034208.A16593@unthought.net \
    --to=jakob@unthought.net \
    --cc=anton@samba.org \
    --cc=ben@kalifornia.com \
    --cc=dlitz@dlitz.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