Trond Myklebust <[email protected]> wrote: > - the NFSv4 delegation model breaks: the client will be using > OPEN when it could use cached opens. More importantly, when > performing an operation that requires it to return the > delegation on the aliased file, it won't know until the server > sends it a callback. Perhaps sharing could be the default on NFSv4 and non-sharing for 2 & 3? After all, NFSv4 is supposed to be able to handle local caching on disk. David - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- Re: recent nfs change causes autofs regression
- From: Trond Myklebust <[email protected]>
- recent nfs change causes autofs regression
- From: "Hua Zhong" <[email protected]>
- Re: recent nfs change causes autofs regression
- From: Trond Myklebust <[email protected]>
- Re: recent nfs change causes autofs regression
- From: Linus Torvalds <[email protected]>
- Re: recent nfs change causes autofs regression
- From: Trond Myklebust <[email protected]>
- Re: recent nfs change causes autofs regression
- From: Linus Torvalds <[email protected]>
- Re: recent nfs change causes autofs regression
- From: Trond Myklebust <[email protected]>
- Re: recent nfs change causes autofs regression
- From: Linus Torvalds <[email protected]>
- Re: recent nfs change causes autofs regression
- From: Jakob Oestergaard <[email protected]>
- Re: recent nfs change causes autofs regression
- From: Linus Torvalds <[email protected]>
- Re: recent nfs change causes autofs regression
- Prev by Date: Re: [-mm PATCH] Memory controller improve user interface (v3)
- Next by Date: Re: recent nfs change causes autofs regression
- Previous by thread: Re: recent nfs change causes autofs regression
- Next by thread: Re: recent nfs change causes autofs regression
- Index(es):
 |