From: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>
To: Pavel Shilovsky <piastryyy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/5] CIFS: Add strictcache mount option
Date: Wed, 03 Nov 2010 11:11:34 +0530 [thread overview]
Message-ID: <4CD0F60E.9040901@suse.de> (raw)
In-Reply-To: <AANLkTi=04ko7zXRaXvgEBzXFfhhL3QU64gnZOXMPoNOD-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> ---
> 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
next prev parent reply other threads:[~2010-11-03 5:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 19:42 [PATCH 1/5] CIFS: Add strictcache mount option Pavel Shilovsky
[not found] ` <AANLkTi=04ko7zXRaXvgEBzXFfhhL3QU64gnZOXMPoNOD-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-11-01 17:09 ` Jeff Layton
2010-11-03 5:41 ` Suresh Jayaraman [this message]
[not found] ` <4CD0F60E.9040901-l3A5Bk7waGM@public.gmane.org>
2010-11-03 5:57 ` Pavel Shilovsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CD0F60E.9040901@suse.de \
--to=sjayaraman-l3a5bk7wagm@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=piastryyy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox