Xref: utzoo comp.protocols.nfs:1211 comp.protocols.tcp-ip.ibmpc:3621
Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!sun-barr!newstop!east!hinode!geoff
From: geoff@hinode.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Newsgroups: comp.protocols.nfs,comp.protocols.tcp-ip.ibmpc
Subject: Re: PC-NFS, buffers and caches
Message-ID: <2488@east.East.Sun.COM>
Date: 27 Aug 90 12:24:51 GMT
References: <1977@dutrun.UUCP>
Sender: news@east.East.Sun.COM
Reply-To: geoff@east.sun.com (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Followup-To: comp.protocols.nfs
Organization: Sun Microsystems PC-NFS Engineering
Lines: 34

Quoth rcdswal@dutrun.UUCP (G.v.d.Wal.) (in <1977@dutrun.UUCP>):
#This may have been asked before, but ..
#
#One of our clients wants to use PC-NFS next to a
#rather memory demanding application.
#The two don't fit in memory together even in a barebone stripped
#system.
#
#The book says "PCNFS.SYS is approximately 75 KB (after allocating
#buffer and cache structures)"
#We discovered tha PC-NFS allocates buffers for drives D - V, ....

Not true. PC-NFS tells DOS that it is a block device handling
units D to V, but it doesn't allocate any buffers for these
drives. It includes certain internal data structures for
8 drives, but this space is hard-coded and cannot be
reconfigured. It also includes a number of buffers, but the
number is not configurable.

#....  where
#our client needs only drive D.

Specifying LASTDRIVE=D will save a little space in DOS, which uses this
to determine how much space to allocate for the logical drive table.
You can also free up some space in PC-NFS by telling it that not to
reserve space for file locks or IP fragment reassembly buffers.
(Assuming you don't need them, of course!) This is all documented under
"Customizing PC-NFS" in the manual.


-- Geoff Arnold, PC-NFS architect, Sun Microsystems. (geoff@East.Sun.COM)   --

To receive a full copy of my .signature, please dial 1-900-GUE-ZORK.
Each call will cost you one zorkmid.