mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: cesar.da.silva@cyberdude.com
Cc: kernellist <linux-kernel@vger.kernel.org>
Subject: Re: Please help me fill in the blanks.
Date: Sat, 26 May 2001 22:27:09 -0400	[thread overview]
Message-ID: <3B1065FD.3F8D7EDF@mandrakesoft.com> (raw)
In-Reply-To: <20010527021808.80979.qmail@web13407.mail.yahoo.com>

Cesar Da Silva wrote:
> The features that I'm wondering about are:
> * Dynamic Processor Resilience

is this fault tolerance?  I think if a CPU croaks, you are dead.

There are patches for hot swap cpu support, but I haven't seen any CPU
fault tolerance patches that can handle a dead processor

> * Dynamic Memory Resilience

RAM fault tolerance?  There was a patch a long time ago which detected
bad ram, and would mark those memory clusters as unuseable at boot. 
However that is clearly not dynamic.

If your memory croaks, your kernel will experience random corruptions

> * Dynamic Page Sizing

no

> * Live Upgrade

LOBOS will let one Linux kernel boot another, but that requires a boot
step, so it is not a live upgrade.  so, no, afaik

> * Alternative I/O Pathing

be less vague

> * HSM

patches exist, I believe

> * TCP selective acknowledgement (SACK)

yes

> * Service Location Protocol (SLP)

don't know

> * ATM IP switching

yes, I believe

> * SOCKS 5 support

yes, via userspace apps/libs

> * Multilink PPP

yes

> * TCP/IP Gratuitous ARP (RFC 2002)

not sure

> * Path MTU Discovery (RFC 1191)

yes

> * Path MTU Discovery over UDP

not sure, but I think so

> * IP Multipath Routing

yes

> The questions I have about the features above are:
> * Are any of the above features implemented in the
> kernel? If yes, where can I read (url-link  to the
> article, paper... please) about it?

http://google.com/

-- 
Jeff Garzik      | Disbelief, that's why you fail.
Building 1024    |
MandrakeSoft     |

  reply	other threads:[~2001-05-27  2:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-27  2:18 Cesar Da Silva
2001-05-27  2:27 ` Jeff Garzik [this message]
2001-05-27  8:17   ` James Sutherland
2001-05-27  8:27   ` Ingo Oeser
2001-05-27  8:57   ` Dominik Kubla
2001-05-27 17:21   ` Ville Herva
2001-05-27 17:26     ` Cesar Da Silva
2001-05-27 17:31   ` Cesar Da Silva
2001-05-27  2:50 ` Jonathan Morton
2001-05-27  2:55   ` Jeff Garzik
2001-05-27 15:49 ` Rik van Riel
2001-05-27 15:55   ` Cesar Da Silva

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=3B1065FD.3F8D7EDF@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=cesar.da.silva@cyberdude.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

all inboxes | Powered by JetHome®