From: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>
To: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH] cifs: document 'fsc' mount option
Date: Tue, 27 Jul 2010 19:20:00 +0530 [thread overview]
Message-ID: <4C4EE408.7070109@suse.de> (raw)
Document the newly added local caching feature using FS-Cache. This patch
could be queued and considered once the local caching patches gets merged
upstream.
Signed-off-by: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>
---
doc/mount.cifs.8.xml | 17 +++++++++++++++++
1 files changed, 17 insertions(+), 0 deletions(-)
diff --git a/doc/mount.cifs.8.xml b/doc/mount.cifs.8.xml
index 4937550..2200746 100644
--- a/doc/mount.cifs.8.xml
+++ b/doc/mount.cifs.8.xml
@@ -534,6 +534,23 @@ permissions in memory that can't be stored on the server. This information can d
maximum wsize currently allowed by CIFS is 57344 (fourteen
4096 byte pages)</para></listitem>
</varlistentry>
+ <varlistentry>
+ <term>fsc</term>
+
+ <listitem><para>Enable local disk caching using FS-Cache
+ for cifs. This option could be useful to improve performance
+ on a slow link, heavily loaded server and/or network
+ where reading from the disk is faster than reading from the
+ server (over the network). This could also impact the
+ scalability positively as the number of calls to the server
+ are reduced. But, be warned that local caching is not suitable
+ for all workloads, for e.g., read-once type workloads. So
+ you need to consider carefully the situation/workload before
+ using this option.
+ NOTE: You also need to have cachefilesd daemon installed and
+ running to make the cache operational.
+ </para></listitem>
+ </varlistentry>
<varlistentry>
<term>--verbose</term>
<listitem><para>Print additional debugging information for the mount. Note that this parameter must be specified before the -o. For example:</para><para>mount -t cifs //server/share /mnt --verbose -o user=username</para></listitem>
next reply other threads:[~2010-07-27 13:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 13:50 Suresh Jayaraman [this message]
[not found] ` <4C4EE408.7070109-l3A5Bk7waGM@public.gmane.org>
2010-07-27 14:33 ` [PATCH] cifs: document 'fsc' mount option Jeff Layton
[not found] ` <20100727103313.4b730ea8-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-07-27 15:13 ` Steve French
[not found] ` <AANLkTina2EyHkrgNAcrY8ZRK=fXQS71dekWc+kOA0+mz-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-27 15:15 ` Jeff Layton
[not found] ` <20100727111517.4fe0859e-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-07-27 15:21 ` Steve French
[not found] ` <AANLkTik9JqtqAtKJQsaQR8aC8s0kwmrcU=_=QQei7U07-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-27 15:34 ` Jeff Layton
2010-07-27 16:33 ` Suresh Jayaraman
2010-07-27 16:38 ` Steve French
[not found] ` <AANLkTi=+Y1XdFCT1UfWZW==qusXfs6t-vxa_CYo03TTT-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-27 21:59 ` Randy Dunlap
2010-07-30 9:49 ` Suresh Jayaraman
2010-07-27 16:42 ` Jeff Layton
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=4C4EE408.7070109@suse.de \
--to=sjayaraman-l3a5bk7wagm@public.gmane.org \
--cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=smfrench-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