Newsgroups: comp.protocols.nfs
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!seth
From: seth@ctr.columbia.edu (Seth Robertson)
Subject: Re: How many nfsd's awake on NFS request - REVISITED
Message-ID: <1991Mar21.110348.568@ctr.columbia.edu>
Organization: Columbia University Center for Telecommunications Research
References: <1991Mar19.092159.254@csc.canterbury.ac.nz>
Date: Thu, 21 Mar 91 11:03:48 GMT

[ Highly paraphrased: ]

> Why is nfs_wakeup_one_nfsd set to zero?  nfs_wakeup_one_biod is set
> to one?

I just looked at this under 4.0.3 (my 4.1.X source is delayed, grr.)
and it appears that there is a problem with the wakeup_one() routine
(the XXX comment says that it should be redone to use
so_wupault->wup_func (a function called instead of wakeup)) On the
other hand, I can find no place in the kernel where this variable is
set and the only place it was used was in this one file.

However, this does not answer the question of whether setting this to
one will cause it not to work or whether so_wupault->wup_func (which
is called if set) is used and whether it wakes up all or just one.


As a test, I set nfs_wakeup_one_nfsd to one and made some nfs
operations.  Nothing obviously broke and the access times via nfs
seemed equivalent on a gross scale...


Does anybody else have a better idea of what is happening?

                                        -Seth Robertson
                                         seth@ctr.columbia.edu