Please help me fill in the blanks.

Please help me fill in the blanks.

[Cesar Da Silva]

Hi again.
I am doing a thesis about comparing the Linux kernel
against HP-UX, AIX, Tru64 UNIX, and Solaris (as you
probably alredy know).
I'm stuck now (and the thesis has to bee ready until
tomorow) with some few features that the other
operating system have, and I can't find any
information about it, if those features are
implemented in Linux or not.

The features that I'm wondering about are:
* Dynamic Processor Resilience
* Dynamic Memory Resilience
* Dynamic Page Sizing
* Live Upgrade
* Alternative I/O Pathing
* HSM
* TCP selective acknowledgement (SACK)
* Service Location Protocol (SLP)
* ATM IP switching
* SOCKS 5 support
* Multilink PPP
* TCP/IP Gratuitous ARP (RFC 2002)
* Path MTU Discovery (RFC 1191)
* Path MTU Discovery over UDP
* IP Multipath Routing

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?
* Is any of the features implemented through a program
/daemon? If yes, which program (link to program)?

Here is the link to my thesis if anyone hasn't got my
previous message:

http://www.student.hig.se/~na98csa/{
,Linux.tex,xjobb.ps}

Thanks in advance,
Cesar da Silva

_____________________________________________________
Do You Yahoo!?
Ditt_namn@yahoo.se - skaffa en gratis mailadress på http://mail.yahoo.se

Re: Please help me fill in the blanks.

[Jeff Garzik]

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     |

Re: Please help me fill in the blanks.

[Jonathan Morton]

>> * 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

If you build nearly everything (except, obviously what you need to boot) as
modules, you can unload modules, build new versions, and reload them.  So,
you could say that partial support for "live upgrades" is included.

It works, too - I unloaded my OV511 driver a few weeks ago, copied the
source for the new one in, built it, and re-inserted it.  Same goes for the
DRM module a couple of weeks before that.  Now, the machine in question
gets rebooted fairly often in any case, but those were things I *didn't*
have to reboot for.

--------------------------------------------------------------
from:     Jonathan "Chromatix" Morton
mail:     chromi@cyberspace.org  (not for attachments)
big-mail: chromatix@penguinpowered.com
uni-mail: j.d.morton@lancaster.ac.uk

The key to knowledge is not to rely on people to teach you it.

Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/

-----BEGIN GEEK CODE BLOCK-----
Version 3.12
GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS
PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)
-----END GEEK CODE BLOCK-----

Re: Please help me fill in the blanks.

[Jeff Garzik]

Jonathan Morton wrote:
> 
> >> * 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
> 
> If you build nearly everything (except, obviously what you need to boot) as
> modules, you can unload modules, build new versions, and reload them.  So,
> you could say that partial support for "live upgrades" is included.

I stand corrected, though I clearly know better:
Modules are unloaded/reloaded all the time during my driver development
:)

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

Re: Please help me fill in the blanks.

[James Sutherland]

On Sat, 26 May 2001, Jeff Garzik wrote:

> 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

The S/390 has this; presumably it applies to Linux as well as the other
supported OSs?

> > * 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

ECC can be supported by the hardware; no support for mapping out duff
banks on x86, but again S/390 may differ?

> > * 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

Live SOFTWARE upgrade, or live HARDWARE upgrade? If the latter, things
like hotswap PCI, USB... and again the S/390?

> > * Service Location Protocol (SLP)
>
> don't know

Yes, I think so - mars_nwe surely needs this?

> > * TCP/IP Gratuitous ARP (RFC 2002)
>
> not sure

Isn't that how LVS clusters handle IP takeovers?

> > * Path MTU Discovery (RFC 1191)
>
> yes

With one or two RFC violations, yes.

Basically, most of those features relating to hardware resilience should
be usable with Linux on an S/390 - they are hardware features, though,
AFAICS?


James.

Re: Please help me fill in the blanks.

[Ingo Oeser]

On Sat, May 26, 2001 at 10:27:09PM -0400, Jeff Garzik wrote:
> > * Service Location Protocol (SLP)

www.openslp.org

Regards

Ingo Oeser
-- 
To the systems programmer,
users and applications serve only to provide a test load.

Re: Please help me fill in the blanks.

[Dominik Kubla]

On Sat, May 26, 2001 at 10:27:09PM -0400, Jeff Garzik wrote:
> 
> > * Service Location Protocol (SLP)
> 
> don't know

Userspace: http://www.openslp.org/

> > * TCP/IP Gratuitous ARP (RFC 2002)
> 
> not sure

Userspace. Also no tool comes to my mind, arping should be easily modified
to do this.

Dominik
-- 
          A lovely thing to see:                   Kobayashi Issa
     through the paper window's holes               (1763-1828)
                the galaxy.               [taken from: David Brin - Sundiver]

Re: Please help me fill in the blanks.

[Rik van Riel]

On Sun, 27 May 2001, [iso-8859-1] Cesar Da Silva wrote:

> I am doing a thesis about comparing the Linux kernel
> against HP-UX, AIX, Tru64 UNIX, and Solaris (as you
> probably alredy know).
> I'm stuck now (and the thesis has to bee ready until
> tomorow)

Aren't you the same guy who posted this question last
week?

And the same guy who asked us to "fill in the blanks"
on an essentially EMPTY work? ;)

Rik
--
Virtual memory is like a game you can't win;
However, without VM there's truly nothing to lose...

http://www.surriel.com/		http://distro.conectiva.com/

Send all your spam to aardvark@nl.linux.org (spam digging piggy)

Re: Please help me fill in the blanks.

[Cesar Da Silva]

 --- Rik van Riel <riel@conectiva.com.br> skrev: > On
Sun, 27 May 2001, [iso-8859-1] Cesar Da Silva
> wrote:
> 
> > I am doing a thesis about comparing the Linux
> kernel
> > against HP-UX, AIX, Tru64 UNIX, and Solaris (as
> you
> > probably alredy know).
> > I'm stuck now (and the thesis has to bee ready
> until
> > tomorow)
> 
> Aren't you the same guy who posted this question
> last
> week?
> 
> And the same guy who asked us to "fill in the
> blanks"
> on an essentially EMPTY work? ;)

Yes, but this time I was more precise with what I
wanted help with (I included a list in the message),
and it helped, I got alot more responses this time.

Regards,
Cesar da Silva

_____________________________________________________
Do You Yahoo!?
Ditt_namn@yahoo.se - skaffa en gratis mailadress på http://mail.yahoo.se

Re: Please help me fill in the blanks.

[Ville Herva]

> > * 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 you are referring to Badram patch by Rick van Rein
(http://rick.vanrein.org/linux/badram/), it doesn't detect the bad ram,
memtest86 does that part (and does it well) -- you enter then enter the
badram clusters as boot param. But I have to say badram patch works
marvellously (thanks, Rick.) Shame it didn't find its way to standard
kernel.

 
-- v --

v@iki.fi

Re: Please help me fill in the blanks.

[Cesar Da Silva]

 --- Ville Herva <vherva@mail.niksula.cs.hut.fi>
skrev: > > > * 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 you are referring to Badram patch by Rick van
> Rein
> (http://rick.vanrein.org/linux/badram/), it doesn't
> detect the bad ram,
> memtest86 does that part (and does it well) -- you
> enter then enter the
> badram clusters as boot param. But I have to say
> badram patch works
> marvellously (thanks, Rick.) Shame it didn't find
> its way to standard
> kernel.

Hi Ville, and thanks for the great link and the
information. 

Regards,
Cesar da Silva

_____________________________________________________
Do You Yahoo!?
Ditt_namn@yahoo.se - skaffa en gratis mailadress på http://mail.yahoo.se

Re: Please help me fill in the blanks.

[Cesar Da Silva]

Thank you Jeff for your very helpfull answer.

 --- Jeff Garzik <jgarzik@mandrakesoft.com> skrev: >
Cesar Da Silva wrote:

> > * Alternative I/O Pathing
> 
> be less vague

What I mean with the above (my defenition) is:
[Alternative I/O Pathing allows the operating system
to re-route the I/O of devices, such as disk or
network adapters, to a backup device, in case of
failure.

Regards,
Cesar da Silva

_____________________________________________________
Do You Yahoo!?
Ditt_namn@yahoo.se - skaffa en gratis mailadress på http://mail.yahoo.se