Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bbn!oberon!cit-vax!ucla-cs!zen!ucbvax!decvax!eagle_snax!geoff
From: geoff@eagle_snax.UUCP ( R.H. coast near the top)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: PC-NFS NET PCNET command
Message-ID: <212@eagle_snax.UUCP>
Date: Sun, 25-Oct-87 21:10:28 EST
Article-I.D.: eagle_sn.212
Posted: Sun Oct 25 21:10:28 1987
Date-Received: Tue, 27-Oct-87 06:42:26 EST
References: <8710231325.AA07476@uc.msc.umn.edu>
Lines: 22
Summary: it's really a performance question

In article <8710231325.AA07476@uc.msc.umn.edu>, jpt@UMN-REI-UC.ARPA (Joseph P. Thomas) writes:
> 
> 	My PC-NFS V2.0 manual says that 'net pcnet [ on | off ]' allows
> PN-NFS to run simultaneously with the IBM PC Network Program.

It's actually a small performance issue. We tried installing PC-NFS in
a PC and then running the IBM PC Network Program (talking to a Sytek
card) on top of it. The PC Network program thinks that the PC-NFS
drives are local PC disks, which allows it to publish them to other
nodes on the PC Network and gateway through to the NFS world. It turned out
that the PC Network program did certain directory searching operations
in a rather unusual way that caused us to flush our own directory search
cache rather faster than usual, slowing down directory searches on the PC 
Network clients. We added some code to our own directory search logic to
cater for this; since it was sub-optimal for other applications we added
the NET PCNET ON|OFF feature to toggle its use.

-- 
Geoff Arnold, Sun Microsystems       | "Picture a bright blue ball,
East Coast Division (home of PC-NFS) |  Spinning, spinning free;
UUCP: {ihnp4,decwrl,...}!sun!garnold |  Dizzy with possibility...
ARPA: garnold@sun.com                |  Ashes, ashes, all fall down..."