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. -- Suresh Jayaraman -- 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
