Path: utzoo!attcan!uunet!wuarchive!brutus.cs.uiuc.edu!tut.cis.ohio-state.edu!cs.utexas.edu!ico!ism780c!darryl
From: darryl@ism780c.isc.com (Darryl Richman)
Newsgroups: comp.unix.i386
Subject: Re: 16-bit memory, caches, and UNIX V/386
Message-ID: <32256@ism780c.isc.com>
Date: 25 Aug 89 00:48:16 GMT
References: <13274@megaron.arizona.edu> <9639@b-tech.ann-arbor.mi.us> <8746@saturn.ucsc.edu> <5801@ficc.uu.net> <9642@b-tech.ann-arbor.mi.us>
Reply-To: darryl@ism780c.UUCP (Darryl Richman)
Organization: Interactive Systems Corp., Santa Monica CA
Lines: 18

In article <9642@b-tech.ann-arbor.mi.us> zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff) writes:
>>I'd like a way to differentiate between the 32-bit and 16-bit memory and use
>>them for different purposes.  You could isolate your 16-bit memory from
>
>If the Unix vendors would just start allocating memory from the top so that
>the disk buffers and kernel would end up in 16 bit memory, things would work
>much better.  Seems like a simple change - how about it Interactive?

MEMRANGEs marked with `:1' in your /etc/default/boot file are used
preferentially for the kernel, since the mark indicates that the memory
cannot be DMAed.  Don't expect your disk buffers to end up there, however.

		--Darryl Richman 
-- 
Copyright (c) 1989 Darryl Richman    The views expressed are the author's alone
darryl@ism780c.isc.com 		      INTERACTIVE Systems Corp.-A Kodak Company
 "For every problem, there is a solution that is simple, elegant, and wrong."
	-- H. L. Mencken