From: "Björn JACKE" <bj-PS7XAnAlDA+VvDNblw4Uiw@public.gmane.org>
To: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
phireph0x-/E1597aS9LQAvxtiuMwx3w@public.gmane.org,
piastry-7qunaywFIewox3rIn2DAYQ@public.gmane.org
Subject: Re: [PATCH] cifs: lower default wsize when unix extensions are not used
Date: Wed, 23 Nov 2011 19:34:05 +0100 [thread overview]
Message-ID: <E1RTHe2-004p4M-7T@intern.SerNet.DE> (raw)
In-Reply-To: <20111109160408.44947815-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
On 2011-11-09 at 16:04 -0500 Jeff Layton sent off:
> On Wed, 9 Nov 2011 14:55:36 -0600
> Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > How much of a performance hit does this make? I would expect that
> > dropping the writesize by more than 50% to most non-Samba servers to
> > work around a bug in Solaris seems extreme. If this hurts our
> > performance measurably, it may be more pragmatic to limit the wsize
> > change to a subset of these (e.g. based on server type) - seems more
> > fair to not punish other servers for a Solaris bug.
> >
>
> I'm not sure how big a hit it will be, but it won't be 0. As always, it
> depends on workload. The problem is, I'm not sure we can reliably
> detect when the server can't handle larger writes like this.
I've seen a performance drop from 60MB/s to 50MB/s on a 1GB switched network
when unix extensions were disabled just because the rsize was limited from 128k
to 64k. That was tested with Darwin's smbfs but the dropdown in performance of
cifs vfs will be similar. If this can be seen as a server bug I'd also like to
see Oracle fix their server and keep cifs vfs be able to use 128k.
Björn
next prev parent reply other threads:[~2011-11-23 18:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 18:37 [PATCH] cifs: lower default wsize when unix extensions are not used Jeff Layton
[not found] ` <1320863843-29406-1-git-send-email-jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-11-09 18:41 ` Jeff Layton
[not found] ` <20111109134140.2105ed9e-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2011-11-09 20:55 ` Steve French
[not found] ` <CAH2r5mtmboSEMHbj6ixh6UGSgiTFz1Mn=ZU6fkQaCSu7n6h=EQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-09 21:04 ` Jeff Layton
[not found] ` <20111109160408.44947815-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2011-11-09 21:14 ` Steve French
[not found] ` <CAH2r5mtGbo4uHzp9KE_Jo3x=hkBewDM8+nvqoVqkyuG4TeRXhQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-09 21:34 ` Jeff Layton
[not found] ` <CAH2r5mupsXVYYkkqdC9fQ=EHfeD6ZeCzV7ggYc0wX_0NR4mhmw@mail.gmail.com>
[not found] ` <CAH2r5mupsXVYYkkqdC9fQ=EHfeD6ZeCzV7ggYc0wX_0NR4mhmw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-09 21:41 ` Jeff Layton
2011-11-23 18:34 ` Björn JACKE [this message]
[not found] ` <E1RTHe2-004p4M-7T-dqLtpHMqGvUyWpdLl23E4A@public.gmane.org>
2011-11-23 20:04 ` Jeff Layton
[not found] ` <CAH2r5muKFRup1BwPqGuiy=+kh-NHP4fs42CC-xpZO1ryN-JK-Q@mail.gmail.com>
[not found] ` <CAH2r5muKFRup1BwPqGuiy=+kh-NHP4fs42CC-xpZO1ryN-JK-Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-24 12:20 ` Jeff Layton
[not found] ` <20111124072036.0fa2ad0d-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2011-11-25 2:30 ` Steve French
2011-11-09 19:06 ` Pavel Shilovsky
2011-11-09 23:10 ` Shirish Pargaonkar
[not found] ` <CADT32eLBeJoeiJUHM5OvK=7vGG1Z5X2NUVh6Hnkfp89u1yySww-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-09 23:57 ` 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=E1RTHe2-004p4M-7T@intern.SerNet.DE \
--to=bj-ps7xanalda+vvdnblw4uiw@public.gmane.org \
--cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=phireph0x-/E1597aS9LQAvxtiuMwx3w@public.gmane.org \
--cc=piastry-7qunaywFIewox3rIn2DAYQ@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.