Caller context flags [PSARC/2007/632 FastTrack timeout 11/09/2007]

[James Carlson]

james wahlig writes:
> return EAGAIN.  When the NFSv2 server gets this, it will simply drop the 
> response, causing the client to reissue the request.  When the NFSv3 
> server gets the EAGAIN w/CC_WOULDBLOCK, it will return the error 
> NFS3ERR_JUKEBOX to the client.  The NFSv3 client knows to retry when it 
> sees this error.  The NFSv4 server will return NFS4ERR_DELAY when it 
> gets this error from the monitor.

That seems to answer the question; thanks.  The answer is that the
wait period is handled by forcing the client to retry.

> The point is, the only caller that will use these flags are ones that 
> are built to handle it.  That is, if they get EAGAIN, they have a 
> mechanism for retrying.

Right ... the part I was missing was how they know _when_ to retry,
because the mechanism doesn't specify a means to allow for that.

Knowing that the retries are pushed back to the client which will just
try every now and again answers the question.

Thanks.

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677