From: Anomalous Force <anomalous_force@yahoo.com>
To: david.lang@digitalinsight.com, jdike@karaya.com
Cc: wa@almesberger.net, alan@lxorguk.ukuu.org.uk,
riel@conectiva.com.br, ebiederm@xmission.com,
linux-kernel@vger.kernel.org
Subject: Re: holy grail
Date: Sun, 29 Dec 2002 20:39:08 -0800 (PST) [thread overview]
Message-ID: <20021230043908.77703.qmail@web13206.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0212291948060.14400-100000@dlang.diginsite.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 2176 bytes --]
--- David Lang <david.lang@digitalinsight.com> wrote:
>
> I think people are at the point of working on this becouse it
> sounds like
> a worthwhile feature, not becouse it's actually anything that would
> be
> used.
UML sounds like a worthwhile feature, turns out its actually pretty
useful too. kexec() is supported in its current incarnation. why
not simply extend it the one step further?
>
> what possible application needs to be able to do a seamless kernel
> upgrade
> that wouldn't be useing a network?
"programs will never use more than 640K of memory." - bill gates
lets talk clusters... the teragrid system being built out of 2024
redhat 7.2 installs (ncsa alone, not counting the 3 other cluster
sites). imagine a simple system on the network to push a copy of the
new kernel and then telling each node to hot-swap. 0 downtime.
__super__ easy to maintain. how easy would that become??? how about
this... an nfs mount point in the grid for /boot such that each node
then gets the kernel from a central point and hot swaps when a flag
is set, or a change is detected in the /boot directory. no push even
needed then. the cost savings from that alone would be worth the
effort to them.
>
> if it's a batch processing task, it can checkpoint itself and
> restart
> after a reboot.
>
2024 nodes rebooting, how much time needed while the system is in a
degraded state?
> if it's a controller of specialized equipment then you either can
> have the
> process checkpoint itself, or you can't afford to pause long enough
> to do
> the kernel swap (i.e. the device keeps operating regardless and so
> may
> generate ssignals to the program during the time when you are
> swapping
> kernels)
>
hence a queue to catch pending irqs while the system swaps over.
=====
Main Entry: anom·a·lous
1 : inconsistent with or deviating from what is usual, normal, or expected: IRREGULAR, UNUSUAL
2 (a) : of uncertain nature or classification (b) : marked by incongruity or contradiction : PARADOXICAL
synonym see IRREGULAR
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
next prev parent reply other threads:[~2002-12-30 4:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 0:51 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 [this message]
2002-12-30 17:57 ` Eric W. Biederman
2002-12-30 13:30 ` Alan Cox
2002-12-29 23:53 ` Werner Almesberger
2002-12-27 13:24 ` Pavel Machek
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=20021230043908.77703.qmail@web13206.mail.yahoo.com \
--to=anomalous_force@yahoo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=david.lang@digitalinsight.com \
--cc=ebiederm@xmission.com \
--cc=jdike@karaya.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=wa@almesberger.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
Powered by JetHome