Re: Eliminating the BKL from the NFS and RPC clients

[Christoph Hellwig <hch@infradead.org>]

On Fri, Jan 19, 2007 at 12:36:20AM -0500, Trond Myklebust wrote:
> No. Attributes may change at any moment on the server. That is _very_
> different to the case where the user or the client changes the
> attributes via setattr. For one thing, we don't have to notify the
> server. Secondly, we do want to be able to update those attributes from
> asynchronous contexts (for instance when a WRITE request returns with
> updated).
> The client should in any case _never_ be overriding the server
> attributes. The only exception to that rule is if we have cached writes
> which change the file size. We do try to detect that...

Sorry, my previous mail wasn't clear enough on how I want setattr
used here.  I think it's right to make all these attribute updates through
->setattr so filesystem can deal with them explicitly.  Of course we'd
still need to treat explicit updates different from implicit one,
probably by adding in ATTR_IMPLIZIT for the later.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs