All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
To: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 4/4] cifs: remove /proc/fs/cifs/Experimental
Date: Tue, 7 Dec 2010 19:09:29 -0500	[thread overview]
Message-ID: <20101207190929.59caaea4@corrin.poochiereds.net> (raw)
In-Reply-To: <AANLkTimUKtFdX4fYtVHQPp0K3KrAhi8xG=YXHT9199Gj-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Tue, 7 Dec 2010 14:31:25 -0600
Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

> On Tue, Dec 7, 2010 at 1:10 PM, Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org> wrote:
> > On Tue, 7 Dec 2010 10:21:11 -0600
> > Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> >
> >> The issue of how to prevent a page from being modified as it is
> >> written out (due to signing in our case) has been discussed on lkml a
> >> few times (e.g. T10 block devices).   We should hold off on changing
> >> this until we have a way of handling the case of:   we calculate the
> >> signature, but just before the page in the cache is remodified, we
> >> send it with the wrong signature ... obviously if we reissue the write
> >> we are fine (the data is fine) but there may be better ways to lock
> >> the page (and some suggestions have been made on lkml for similar
> >> sounding problems).
> >>
> >
> > This behavior has been "Experimental" for years. At what point do we
> > remove this kludge? Who in their right mind is going to turn on a
> > switch called "Experimental" to enable this? As a user, I'd certainly
> > be reticent to do so. It's not clear what turning on "Experimental"
> > would give me.
> 
> 20%+ better write performance
> 
> > If you think this behavior deserves to be switchable then let's put a
> > real usable switch on it. I don't think it ought to be hidden
> > as /proc/fs/cifs/Experimental. Perhaps a module parameter for
> > this would be more appropriate?
> 
> Probably best to work through how to fix the general issue on fsevel
> (ie how to write a presumably unstable page from the cache out)
> 
> 
> 

Obviously there needs to be some sort of endgame for this code. It's
not healthy to keep this under "Experimental" for years on end. That
said, I don't really want to tackle that project at the moment. 

I am however interested in moving this code out from under this
"Experimental" procfile. Would you be amenable to a module option for
this? If so, how would you describe this knob? What name should it have?

The main reason I mention module option is that it's now very helpful
to have this sort of knob based on a file under /proc/fs/cifs. It can't
be set at boot time without a special script.

-- 
Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>

      parent reply	other threads:[~2010-12-08  0:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-07 14:23 [PATCH 0/4] cifs: CONFIG_CIFS_EXPERIMENTAL removal Jeff Layton
     [not found] ` <1291731835-1120-1-git-send-email-jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-12-07 14:23   ` [PATCH 1/4] cifs: remove export_ops code Jeff Layton
2010-12-07 14:23   ` [PATCH 2/4] cifs: move "ntlmssp" and "local_leases" options out of experimental code Jeff Layton
2010-12-07 14:23   ` [PATCH 3/4] cifs: remove CIFSSMBQueryReparseLinkInfo and CONFIG_CIFS_EXPERIMENTAL Jeff Layton
2010-12-07 14:23   ` [PATCH 4/4] cifs: remove /proc/fs/cifs/Experimental Jeff Layton
     [not found]     ` <1291731835-1120-5-git-send-email-jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-12-07 16:13       ` Jeff Layton
     [not found]         ` <20101207111328.6647c36c-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-12-07 16:21           ` Steve French
     [not found]             ` <AANLkTi=_5VYCXpd+WfwcKq50=kN3GRaGVgjfkReM9Ye0-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-12-07 19:10               ` Jeff Layton
     [not found]                 ` <20101207141059.0ddc6c7d-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-12-07 20:31                   ` Steve French
     [not found]                     ` <AANLkTimUKtFdX4fYtVHQPp0K3KrAhi8xG=YXHT9199Gj-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-12-08  0:09                       ` Jeff Layton [this message]

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=20101207190929.59caaea4@corrin.poochiereds.net \
    --to=jlayton-eunubhrolfbytjvyw6ydsg@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.