Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!athena.mit.edu!wesommer
From: wesommer@athena.mit.edu (William E. Sommerfeld)
Newsgroups: comp.arch,comp.unix.wizards,comp.os.misc
Subject: Re: Shared libraries (Was: Re: Big Programs Hurt Performance)
Message-ID: <1553@bloom-beacon.MIT.EDU>
Date: Mon, 5-Oct-87 13:12:51 EDT
Article-I.D.: bloom-be.1553
Posted: Mon Oct  5 13:12:51 1987
Date-Received: Thu, 8-Oct-87 02:39:08 EDT
References: <6886@eddie.MIT.EDU) <2501@xanth.UUCP> <2067@sfsup.UUCP> <1535@geac.UUCP> <29944@sun.uucp>
Sender: daemon@bloom-beacon.MIT.EDU
Reply-To: wesommer@athena.mit.edu (William E. Sommerfeld)
Organization: Massachusetts Institute of Technology
Lines: 18
Xref: mnetor comp.arch:2516 comp.unix.wizards:4695 comp.os.misc:268

In article <29944@sun.uucp> guy%gorodish@Sun.COM (Guy Harris) writes:
>	   .... is the Multics TCP/IP code part of the
>	   hardcore supervisor?  

No, it's not.  There is some device driver support (I'm not familiar
with the details) in hardcore, but the bulk of the code runs in the
user ring (or at least outside of hardcore) in a daemon process.
Because of this, it's possible to completely stop TCP, install a new
version, and restart it while the system is still running.  It's also
very unlikely that a failure in the TCP/IP code will cause the entire
system to crash.

As for sizes.. Looking in >lib>net>e on MIT-Multics, I see about 50
records (of 1024 36 bit words each) of object segments which corespond
to the BSD /sys/netinet kernel code.  That's about 230K 8-bit bytes..
about 1/2 of a 4.3BSD+NFS VAX kernel (including the symbol table).

					- Bill