Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!hsdndev!wuarchive!uunet!mcsun!unido!fauern!NewsServ!tritsche
From: tritsche@Informatik.TU-Muenchen.DE (Stefan Tritscher)
Newsgroups: comp.os.mach
Subject: Re: Bytes in Mach 3.0? (mine is smaller than yours, revisited)
Message-ID: <1991Feb19.175717.2996@newsserv.informatik.tu-muenchen.de>
Date: 19 Feb 91 17:57:17 GMT
References: <62753@bbn.BBN.COM| <1991Feb15.214231.21348@watmath.waterloo.edu| <1991Feb16.002946.5711@zoo.toronto.edu|
Sender: news@newsserv.informatik.tu-muenchen.de
Organization: Technische Universitaet Muenchen, Germany
Lines: 45

In article <1991Feb16.002946.5711@zoo.toronto.edu| geoff@zoo.toronto.edu (Geoffrey Collyer) writes:
|Dick Dunn:
||| |My confusion stems from the understanding that the Mach 3.0 kernel
||| |is supposed to be the "micro-kernel" version, and the belief that a 240 Kb
||| |kernel cannot reasonably be labeled "micro".
|
|Fletcher Kittredge:
||| Sure, how familar are you with modern operating systems?  245K of text
||| with 31k of data is *VERY* small for a UNIXoid kernel.  For example,
||| here is the size of the Unix kernel on Sun, DEC and HP systems:
|
|Guy Middleton:
||I don't think it is all that small.  4.3bsd on a VAX has text of similar size:
||
||text	data	bss	dec	hex
||229784	166320	90048	486152	76b08
||
||Note that it is probably more fair to compare 386 with VAX binaries than with
||SPARC, MIPS or HP-PA, since RISC code tends to occupy more space.
|
|Here are some more `macro' kernel sizes, from a Sun 3 running a hybrid
|Ninth Edition system (dak's 9vr1, for those who know what that means):
|
|text	data	bss	dec	hex
|200540	41084	311848	553472	87200	/unix
|
|This kernel is configured for 8 users and includes a very generous
|allotment of streams buffers, a couple on-disk file systems (bitmapped
|and non-bitmapped free lists), /proc, the client side of a network file
|system (netb), TCP/IP, and various goo left over from the Sun system
|(e.g. keyboard mapping line discipline).
|
|Please note that the Mach ``micro-kernel'', at least as recently
|distributed, is claimed to exclude networking and file system code,
|among other things, if memory serves.  So one is left to wonder why a
|micro-kernel which one would expect to be stripped-down and tight, is
|somewhat larger and much less functional than a macro kernel.  One can
[...]
|-- 
|Geoff Collyer		utzoo!geoff, zoo.toronto.edu!geoff

They don't say what they mean with 'micro'.
Maybe they mean micro-functional not micro-size ;->

Sorry - could not resist, Stefan