public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Werner Almesberger <wa@almesberger.net>
To: Anomalous Force <anomalous_force@yahoo.com>
Cc: ebiederm@xmission.com, linux-kernel@vger.kernel.org
Subject: Re: holy grail
Date: Sun, 29 Dec 2002 20:53:28 -0300	[thread overview]
Message-ID: <20021229205328.B1363@almesberger.net> (raw)
In-Reply-To: <20021228163517.66372.qmail@web13207.mail.yahoo.com>; from anomalous_force@yahoo.com on Sat, Dec 28, 2002 at 08:35:17AM -0800

Anomalous Force wrote:
> you miss my point. im not saying to model it after tcp/ip. that
> was just a reference to a method of data exchange wherein the
> data has metadata to describe it.

I understood that. What I was saying is that metadata in a TCP
connection is usually not sufficient for restoring the endpoint
state.

> it makes full sense in an enterprise with 3000+ users that operates
> 24/7/365. no scheduled down-time for kernel upgrades.

I don't disagree with the usefulness of such functionality, but
I disagree with the level at which you suggest to implement this.

The approach of trying to migrate low-level kernel state has the
following problems/disadvantages:

 - complexity
 - does not allow recovery from corrupt kernel state, as Pavel has
   suggested
 - does not support recovery from corrupt hardware state
 - does not support substitution of infrastructure (e.g. what if
   I want to fail over to a different machine, maybe quickly
   replace some non-hotpluggable hardware (*), or even swap that
   old disk with a new one that has completely different
   characteristics ?)

So, compared to an approach that implements this at the kernel to
user space API level, you get a lot of extra complexity, but miss
several very desirable features.

(*) While the "big iron" in your data center may have hot-swappable
    CPUs and everything, it would be nice if such things could also
    be done with commodity hardware that doesn't provide such
    luxury.

> this is not true. if the system were an integral part of the overall
> design, then programming would include it apriori.

Making something part of the design alone doesn't guarantee that
this is a good approach, nor that it will actually work :-)

> there is a fine distinction between kernel migration, and hot-swap.
> in a hot-swap setup, there will be signals pending from devices
[...]

Err, yes, but what does your "hot-swap" do that kernel migration
doesn't ?

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, Buenos Aires, Argentina         wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/

  parent reply	other threads:[~2002-12-29 23:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-27  0:51 holy grail Anomalous Force
2002-12-27  4:03 ` Werner Almesberger
2002-12-27  7:21   ` Anomalous Force
2002-12-27  7:37     ` Ingo Oeser
2002-12-27 11:30     ` Werner Almesberger
2002-12-28 16:35       ` Anomalous Force
2002-12-28 20:43         ` Rik van Riel
2002-12-29 15:56           ` Anomalous Force
2002-12-29 16:44             ` John Bradford
2002-12-30  1:05           ` Alan Cox
2002-12-30  1:32             ` Werner Almesberger
2002-12-30  2:45               ` Jeff Dike
2002-12-30  3:55                 ` David Lang
2002-12-30  4:39                   ` Anomalous Force
2002-12-30 17:57                     ` Eric W. Biederman
2002-12-30 13:30               ` Alan Cox
2002-12-29 23:53         ` Werner Almesberger [this message]
2002-12-27 13:24     ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2002-12-30  5:00 Anomalous Force
2002-12-30  6:46 ` Ed Sweetman

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=20021229205328.B1363@almesberger.net \
    --to=wa@almesberger.net \
    --cc=anomalous_force@yahoo.com \
    --cc=ebiederm@xmission.com \
    --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