Xref: utzoo comp.unix.sysv286:161 comp.unix.sysv386:8334 comp.unix.xenix.misc:212 comp.unix.xenix.sco:2582 comp.unix.wizards:25733
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!tut.cis.ohio-state.edu!sei.cmu.edu!dvk
From: dvk@sei.cmu.edu (Daniel Klein)
Newsgroups: comp.unix.sysv286,comp.unix.sysv386,comp.unix.xenix.misc,comp.unix.xenix.sco,comp.unix.wizards
Subject: Re: Kernel Definition
Message-ID: <25915@as0c.sei.cmu.edu>
Date: 23 May 91 15:59:21 GMT
References: <1423@necis.UUCP>
Sender: netnews@sei.cmu.edu
Organization: CMU Software Engineering Institute
Lines: 18


In article <1423@necis.UUCP>, jjp@necis.UUCP (Jeff Phillips) writes:
|> A friend of mine is writing a paper on balanced system approach.  In it he
|> makes the assertion that "...(the UNIX operating system is) too large to fit 
|> in system RAM all at once, therefore pieces of the operating system are swapped
|> between system RAM and disk, thereby generating even more disk I/O requests."

I believe that your friend is sadly mistaken.  Unless things have changed
radically in the past year or two, the kernel is wholly memory resident.
Some so-called "system" processes are swap/pageable in the same way that
"user" processes are.  Some examples are the FTP daemon, the RLOGIN daemon,
and so forth).  Even these are not true "system" processes.  "System"
processes (like the swapper and page daemon) are not swapped or paged (for
obvious reasons).
-- ============ -- =========== -- =========== -- =========== -- =========== --
"The only thing that separates us from the animals is superstition and
mindless rituals" (Latke)      Daniel Klein	CMU-SEI   +1 412/268-7791
						dvk@sei.cmu.edu