public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Steven Cole <elenstev@mesatop.com>,
	linux-kernel@vger.kernel.org, Larry McVoy <lm@bitmover.com>,
	Linus Torvalds <torvalds@transmeta.com>
Subject: Re: Kernel hot-swap using Kexec, BProc and CC/SMP Clusters.
Date: Mon, 05 May 2003 14:16:28 -0400	[thread overview]
Message-ID: <3EB6AA7C.8070501@nortelnetworks.com> (raw)
In-Reply-To: m1d6ixb8m7.fsf@frodo.biederman.org

Eric W. Biederman wrote:

> The interesting thing becomes how do you measure system uptime.

In telecom at least, as long as the service which you are providing is 
available, you're "up".  The assumption is that you're "always" up, with brief 
(hopefully) interruptions for faults or upgrades.

Because of this, it may turn out that measuring service downtime is more 
meaningful than system uptime.

Chris



-- 
Chris Friesen                    | MailStop: 043/33/F10
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com


  parent reply	other threads:[~2003-05-05 18:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-05 13:18 Kernel hot-swap using Kexec, BProc and CC/SMP Clusters Steven Cole
2003-05-05 14:22 ` Karim Yaghmour
2003-05-05 17:34 ` Eric W. Biederman
2003-05-05 18:00   ` Steven Cole
2003-05-05 18:17     ` Valdis.Kletnieks
2003-05-05 19:51       ` Steven Cole
2003-05-05 20:25         ` Richard B. Johnson
2003-05-05 18:16   ` Chris Friesen [this message]
2003-05-06  1:28   ` Steven Cole
  -- strict thread matches above, loose matches on Subject: below --
2003-05-06  3:19 Stephen M. Kenton
2003-05-06  9:49 ` Eric W. Biederman

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=3EB6AA7C.8070501@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=ebiederm@xmission.com \
    --cc=elenstev@mesatop.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=torvalds@transmeta.com \
    /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