Xref: utzoo comp.unix.sysv286:159 comp.unix.sysv386:8330 comp.unix.xenix.misc:210 comp.unix.xenix.sco:2578 comp.unix.wizards:25731
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!mintaka!bloom-beacon!bu.edu!encore!necis!jjp
From: jjp@necis.UUCP (Jeff Phillips)
Newsgroups: comp.unix.sysv286,comp.unix.sysv386,comp.unix.xenix.misc,comp.unix.xenix.sco,comp.unix.wizards
Subject: Kernel Definition
Message-ID: <1423@necis.UUCP>
Date: 23 May 91 14:15:55 GMT
Reply-To: jjp@necis.UUCP (Jeff Phillips)
Organization: NEC Technologies, Inc., Boxborough, MA
Lines: 16

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

Seven years ago I learned that one of the definitions for kernel is "memory 
resident software".  Is the kernel always memory resident, or do parts of it 
get paged (or swapped) out to the swap partition?  If it does go to the 
swapper, what algorithm is used to determine which kernel subsystem (i/o, 
file, process, or dev.drv's) gets swapped out?
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@ Jeffrey J. Phillips				UUCP: jjp@necis.nec.com   @@
@@ NEC Technologies, Inc.			PHONE: (508)635-6077	  @@
@@          "UNIX isn't a philosophy, it's a way of life" - anon          @@
@@ CASUAL DISCLAIMER: Opinions are mine - definitely not corporate policy @@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@