All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>
To: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/3] cifs: allow fsc mount option only if CONFIG_CIFS_FSCACHE is set
Date: Mon, 29 Nov 2010 22:05:58 +0530	[thread overview]
Message-ID: <4CF3D66E.4060505@suse.de> (raw)
In-Reply-To: <AANLkTimWZYcUFRu1JAzdX2u5POL6UGDq=ESXqMPsc+Ly-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 11/27/2010 09:21 AM, Steve French wrote:
> 
> 
> On Fri, Nov 26, 2010 at 9:50 PM, Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
> <mailto:smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>> wrote:
> 
>     As an alternative - if fsc is stable and no defects and doesn't
>     increase the code size appreciably ... what are the drawbacks of
>     turning it on unconditionally?
> 
> 
> ie always configure it, we still only enable it on a mount when fsc is
> specified on mount
> �

I'm not aware of any open issues w.r.t cifs FS-Cache (except the
problems this patchset addresses) but I'm not sure how much testing it
has undergone really (except for me running all my tests with fsc on for
sometime and a few openSUSE users). The code size is not really much of
a problem.

The strict cache patches accounting for fscache might also provide more
testing ground. So, I think keeping it as non-default atleast for one
more release would be good before we make it as a config default.

Thanks,

>     On Wed, Nov 24, 2010 at 6:19 AM, Suresh Jayaraman
>     <sjayaraman-l3A5Bk7waGM@public.gmane.org <mailto:sjayaraman-l3A5Bk7waGM@public.gmane.org>> wrote:
> 
>         Currently, it is possible to specify 'fsc' mount option even if
>         CONFIG_CIFS_FSCACHE has not been set. The option is being
>         ignored silently
>         while the user fscache functionality to work. Fix this by
>         raising error when
>         the CONFIG option is not set.
> 
> 
>         Reported-by: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
>         <mailto:jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>>
>         Signed-off-by: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org
>         <mailto:sjayaraman-l3A5Bk7waGM@public.gmane.org>>
>         ---
>         �fs/cifs/connect.c | � �5 +++++
>         �1 files changed, 5 insertions(+), 0 deletions(-)
> 
>         diff --git a/fs/cifs/connect.c b/fs/cifs/connect.c
>         index 251a17c..32fa4d9 100644
>         --- a/fs/cifs/connect.c
>         +++ b/fs/cifs/connect.c
>         @@ -1352,6 +1352,11 @@ cifs_parse_mount_options(char *options,
>         const char *devname,
>         � � � � � � � � � � � � � � � �"supported. Instead set "
>         � � � � � � � � � � � � � � � �"/proc/fs/cifs/LookupCacheEnabled
>         to 0\n");
>         � � � � � � � �} else if (strnicmp(data, "fsc", 3) == 0) {
>         +#ifndef CONFIG_CIFS_FSCACHE
>         + � � � � � � � � � � � cERROR(1, "FS-Cache support needs
>         CONFIG_CIFS_FSCACHE"
>         + � � � � � � � � � � � � � � � � "kernel config option set");
>         + � � � � � � � � � � � return 1;
>         +#endif
>         � � � � � � � � � � � �vol->fsc = true;
>         � � � � � � � �} else if (strnicmp(data, "mfsymlinks", 10) == 0) {
>         � � � � � � � � � � � �vol->mfsymlinks = true;
> 
> 
> 
> 
>     -- 
>     Thanks,
> 
>     Steve
> 
> 
> 
> 
> -- 
> Thanks,
> 
> Steve


-- 
Suresh Jayaraman

  parent reply	other threads:[~2010-11-29 16:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-24 12:19 [PATCH 0/3] cifs: fix a few fscache issues Suresh Jayaraman
     [not found] ` <1290601147-11392-1-git-send-email-sjayaraman-l3A5Bk7waGM@public.gmane.org>
2010-11-24 12:19   ` [PATCH 1/3] cifs: allow fsc mount option only if CONFIG_CIFS_FSCACHE is set Suresh Jayaraman
     [not found]     ` <1290601147-11392-2-git-send-email-sjayaraman-l3A5Bk7waGM@public.gmane.org>
2010-11-27 12:12       ` Jeff Layton
     [not found]     ` <AANLkTinysSbT-p=_btJ4YGORDiY5Tz2aT=VagDieUGhY@mail.gmail.com>
     [not found]       ` <AANLkTimWZYcUFRu1JAzdX2u5POL6UGDq=ESXqMPsc+Ly@mail.gmail.com>
     [not found]         ` <AANLkTimWZYcUFRu1JAzdX2u5POL6UGDq=ESXqMPsc+Ly-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-11-29 16:35           ` Suresh Jayaraman [this message]
2010-11-24 12:19   ` [PATCH 2/3] cifs: enable fscache iff fsc mount option is used explicitly Suresh Jayaraman
     [not found]     ` <1290601147-11392-3-git-send-email-sjayaraman-l3A5Bk7waGM@public.gmane.org>
2010-11-27 12:24       ` Jeff Layton
2010-11-24 12:19   ` [PATCH 3/3] cifs: display fsc in /proc/mounts Suresh Jayaraman
     [not found]     ` <1290601147-11392-4-git-send-email-sjayaraman-l3A5Bk7waGM@public.gmane.org>
2010-11-27 12:24       ` 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=4CF3D66E.4060505@suse.de \
    --to=sjayaraman-l3a5bk7wagm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.