2010/11/3 Suresh Jayaraman <sjayaraman@xxxxxxx>: > On 11/01/2010 01:12 AM, Pavel Shilovsky wrote: >> Use for switching on strict cache mode. In this mode the >> client read from the cache all the time it has Oplock Level II, >> otherwise - read from the server. All written data are stored >> in the cache, but if the client doesn't have Exclusive Oplock, >> it writes the data to the server. >> >> Signed-off-by: Pavel Shilovsky <piastryyy@xxxxxxxxx> >> --- >> fs/cifs/README | 5 +++++ >> fs/cifs/cifs_fs_sb.h | 1 + >> fs/cifs/connect.c | 5 +++++ >> 3 files changed, 11 insertions(+), 0 deletions(-) >> >> diff --git a/fs/cifs/README b/fs/cifs/README >> index ee68d10..8fb6192 100644 >> --- a/fs/cifs/README >> +++ b/fs/cifs/README >> @@ -443,6 +443,11 @@ A partial list of the supported mount options follows: >> if oplock (caching token) is granted and held. Note that >> direct allows write operations larger than page size >> to be sent to the server. >> + strictcache Use for switching on strict cache mode. In this mode the >> + client read from the cache all the time it has Oplock Level II, >> + otherwise - read from the server. All written data are stored >> + in the cache, but if the client doesn't have Exclusive Oplock, >> + it writes the data to the server. > > Could you remind me where this will be useful? Also, providing the same > information in README and mount.cifs man page is useful as well. > It is useful when we need to get the only the valida data from the server. Ex. when the first process writes to the server and the second reads this in the same time. Due to Samba server can delay mtime change after writing, we can't trust to mtime and oef checkings and have to process it according to oplock level we have. It also works with the mandatory byte-range locking style which Windows supports - that can let us to make Wine application work togather with Windows ones on CIFS share where byte-range locks play sinchronization role. -- Best regards, Pavel Shilovsky. -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
