Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!oliveb!intelca!mipos3!omepd!littlei!reed!omen!caf
From: caf@omen.UUCP
Newsgroups: comp.unix.xenix
Subject: Re: trying to re-configure the kernel
Message-ID: <529@omen.UUCP>
Date: Tue, 28-Apr-87 15:42:35 EDT
Article-I.D.: omen.529
Posted: Tue Apr 28 15:42:35 1987
Date-Received: Fri, 1-May-87 02:40:57 EDT
References: <2486@cit-vax.Caltech.Edu>
Reply-To: caf@.UUCP (PUT YOUR NAME HERE)
Distribution: world
Organization: Omen Technology Inc, Portland Oregon
Lines: 17

In article <2486@cit-vax.Caltech.Edu> sns@tybalt.caltech.edu (Samuel N. Southard) writes:
:I have lots (7 Meg) of memory and would like to reconfigure my kernel to take 
:advantage of it - the default kernel only has 100K of buffer space.  I am sure
:that, if I had a properley configured kernel I would see a fairly large speed
:increase. 
:
The procedure for increasing the buffer allocation in SCO Xenix is to edit the
"master" file in /usr/sys/conf (or therebaouts) and remake the kernel (mostly
relinking).

With the SYS V 2.1x kernels, one could get up to 200 buffers, I don't know
what the limit is for 2.2.  I've experimented with values up to 500k.

Large values cause the system to lurch when a sync(1) call flushes them out
periodically.  A more intelligent solution is needed here, such as writing
all dirty buffers that have been dirty for 30 seconds, and doing this every
few seconds so there aren't too many to do all at once.