Xref: utzoo comp.unix.sysv286:171 comp.unix.sysv386:8633 comp.unix.xenix.misc:237 comp.unix.xenix.sco:2682 comp.unix.wizards:25831
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!uunet!viusys!uxui!unislc!harem!wes
From: wes@harem.clydeunix.com (Barnacle Wes)
Newsgroups: comp.unix.sysv286,comp.unix.sysv386,comp.unix.xenix.misc,comp.unix.xenix.sco,comp.unix.wizards
Subject: Re: Kernel Definition
Summary: Large virtual tables in kernel?
Message-ID: <311@harem.clydeunix.com>
Date: 31 May 91 21:55:30 GMT
References: <1423@necis.UUCP> <1991May24.065316.27331@thunder.mcrcim.mcgill.edu> <19332@rpp386.cactus.org>
Organization: Clyde's Harem; Eunuchs Guard
Lines: 23

In article <19332@rpp386.cactus.org>, jfh@rpp386.cactus.org (John F Haugh II) writes:
% The AIX v3 kernel is pagable.  It is divided into three "segments", as
% it were.  The first is code that is only required for initialization.
% The second is "pinned" code that must always be present (like the page
% fault handler ;-) and the third is pagable code [ by "code" I mean
% object code - that is, text and data ]
% 
% The various system tables are defined with huge sizes, and the system
% just page faults in the new pages for the kernel tables as it needs
% them, thus ending the dilema about creating new proc table or whateve
% entries by rebuilding the system.  On a typical system the size of the
% kernel is somewheres near 20MB, much of which is never even used - it
% just remains off in virtual la-la land waiting to be referenced ...

But the tables still require page space, right?  V.4's dynamically-sized
tables sound like a better idea.

	Wes Peters
-- 
#include <std/disclaimer.h>                               The worst day sailing
My opinions, your screen.                                   is much better than
Raxco had nothing to do with this!                        the best day at work.
     Wes Peters:  wes@harem.clydeunix.com   ...!sun!unislc!harem!wes