Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!gorodish!guy
From: guy%gorodish@Sun.COM (Guy Harris)
Newsgroups: comp.arch,comp.unix.wizards,comp.os.misc
Subject: Re: Shared libraries (Was: Re: Big Programs Hurt Performance)
Message-ID: <30034@sun.uucp>
Date: Mon, 5-Oct-87 16:50:59 EDT
Article-I.D.: sun.30034
Posted: Mon Oct  5 16:50:59 1987
Date-Received: Thu, 8-Oct-87 07:21:32 EDT
References: <6886@eddie.MIT.EDU) <2501@xanth.UUCP> <2067@sfsup.UUCP> <1553@bloom-beacon.MIT.EDU>
Sender: news@sun.uucp
Lines: 22
Xref: mnetor comp.arch:2519 comp.unix.wizards:4709 comp.os.misc:269

> 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).

Good, somebody has access to real and current data....

	1) How much of the 50 pages are code+data as opposed to symbol table?
	   (I haven't used a Multics system in ages, but I presume it has
	   some way of finding out how much of the segment code and data,
	   right?)

	2) How does the size of the hardcore supervisor plus the TCP/IP code
	   compare to the size of a 4.3BSD kernel (with NFS if the Multics in
	   question includes a similar sort of distributed file system,
	   without NFS if it doesn't)?

I presume the VAX figure is for the entire kernel, not just the "/sys/netinet"
code.
	Guy Harris
	{ihnp4, decvax, seismo, decwrl, ...}!sun!guy
	guy@sun.com