Searched hist:beb2a5ec386e5ce6891ebd1c06b913da04354b40 (Results 1 – 3 of 3) sorted by relevance
| /linux/fs/nfs/ |
| H A D | delegation.h | diff beb2a5ec386e5ce6891ebd1c06b913da04354b40 Tue Jan 03 09:55:37 CET 2006 Trond Myklebust <Trond.Myklebust@netapp.com> NFSv4: Ensure change attribute returned by GETATTR callback conforms to spec
According to RFC3530 we're supposed to cache the change attribute
at the time the client receives a write delegation.
If the inode is clean, a CB_GETATTR callback by the server to the
client is supposed to return the cached change attribute.
If, OTOH, the inode is dirty, the client should bump the cached
change attribute by 1.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
|
| H A D | callback_proc.c | diff beb2a5ec386e5ce6891ebd1c06b913da04354b40 Tue Jan 03 09:55:37 CET 2006 Trond Myklebust <Trond.Myklebust@netapp.com> NFSv4: Ensure change attribute returned by GETATTR callback conforms to spec
According to RFC3530 we're supposed to cache the change attribute
at the time the client receives a write delegation.
If the inode is clean, a CB_GETATTR callback by the server to the
client is supposed to return the cached change attribute.
If, OTOH, the inode is dirty, the client should bump the cached
change attribute by 1.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
|
| H A D | delegation.c | diff beb2a5ec386e5ce6891ebd1c06b913da04354b40 Tue Jan 03 09:55:37 CET 2006 Trond Myklebust <Trond.Myklebust@netapp.com> NFSv4: Ensure change attribute returned by GETATTR callback conforms to spec
According to RFC3530 we're supposed to cache the change attribute
at the time the client receives a write delegation.
If the inode is clean, a CB_GETATTR callback by the server to the
client is supposed to return the cached change attribute.
If, OTOH, the inode is dirty, the client should bump the cached
change attribute by 1.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
|