Re: [nfsv4] Issue 21: pnfs EOF handling

On Tue, 2006-07-11 at 05:33 -0700, Garth Goodson wrote:

> While the semantics may seem better than NFS I don't think they really 
> are.  Basically you are getting what pretty much any NFS server gives 
> you --- the ability for a client that issued a read to see the latest 
> data comitted at the NFS server.  I agree this is better than 
> open-close, but it is what you get today.  Also, since the EOF callback 
> was proposed for blocks, we thought we could make use of it.

What you get today is that the client read will see whatever the server
sees. That is pretty much what you get without a callback at all.

Why does blocks need it?

> You are correct that it would be justifiable to return EOF to the 
> reader.  But as I mentioned earlier, it is slightly harder for the 
> reader to obtain the new EOF (it can't piggyback getattr calls on the 
> read).
> 
> I think we are arguing a minor point here.  The EOF callback is an 
> optimization.

My question is whether or not we need this type of optimisation at all.
If it doesn't add anything useful to the protocol, I'd vote to kill it.

Cheers,
  Trond

_______________________________________________
nfsv4 mailing list
nfsv4@ietf.org
https://www1.ietf.org/mailman/listinfo/nfsv4