Path: utzoo!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac,att!emory!wuarchive!waikato.ac.nz!canterbury!cosc038
From: cosc038@csc.canterbury.ac.nz
Newsgroups: comp.protocols.nfs
Subject: How many nfsd's awake on NFS request - REVISITED
Message-ID: <1991Mar19.092159.254@csc.canterbury.ac.nz>
Date: 18 Mar 91 21:40:58 GMT
Organization: University of Canterbury, Christchurch, New Zealand
Lines: 22

In a recent thread in this newsgroup one of the issues discussed was
about whether all nfsd's, or just one, are awoken when an NFS request
was received.  I seem to remember that one conclusion was that in SunOS
4.X only one nfsd process is awoken when an NFS request is received, but
this doesn't seem to be the _default_ behaviour.  This behavious is
controlled by the kernel variable nfs_wakeup_one_nfsd.  In both SunOs
4.0.3 on a sun3, and SunOS 4.1.1 on a sparc2, the value of this variable
is 0, indicating that all nfsds are awoken when an NFS request is
received.  I'm pretty sure that nfs_wakeup_one_nfsd is 0 in systems
shipped by Sun (i.e.  that the reason nfs_wakeup_one_nfsd is 0 is not
because of some local effect on the kernels). 

So, what are the implications of setting nfs_wakeup_one_nfsd to 1? I
note that there is a variable called nfs_wakeup_one_biod which has the
value 1 for both kernels mentioned above. 

-- 
Paul Ashton
Email(internet): paul@cosc.canterbury.ac.nz
NZ Telecom:     Office: +64 3 667 001 x6350
NZ Post:        Dept of Computer Science
                University of Canterbury, Christchurch, New Zealand