From: Evgeniy Polyakov <zbr@ioremap.net>
To: Steve French <smfrench@gmail.com>
Cc: Shirish Pargaonkar <shirishpargaonkar@gmail.com>,
Jeff Layton <jlayton@redhat.com>,
Suresh Jayaraman <sjayaraman@suse.de>,
nhorman@redhat.com,
"linux-cifs-client@lists.samba.org"
<linux-cifs-client@lists.samba.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Frank S Filz <ffilz@us.ibm.com>
Subject: Re: sendmsg blocking with sendtimeout vs. non-blocking
Date: Thu, 23 Oct 2008 21:46:12 +0400 [thread overview]
Message-ID: <20081023174612.GA14817@2ka.mipt.ru> (raw)
In-Reply-To: <524f69650810231040y60282412td262990a6fe84ee2@mail.gmail.com>
Hi.
On Thu, Oct 23, 2008 at 12:40:05PM -0500, Steve French (smfrench@gmail.com) wrote:
> On Thu, Oct 23, 2008 at 11:42 AM, Steve French <smfrench@gmail.com> wrote:
> > On Thu, Oct 23, 2008 at 11:26 AM, Shirish Pargaonkar
> > As I look into this sndbuf and rcvbuf size setting ... what concerns
> > me is why nfs sets these sizes for snd and rcvbuf sizes still if they
> > don't need to be set? We (cifs) have larger write sizes (56K) than
> > nfs's default. See svc_set_sockbufsize in net/sunrpc/svcsock.c
>
> What is the valid range for the sndbuf and rcvbuf size so I can sanity
> check this if the user overrides it on mount?
>From zero to infinity. Actual size will be automatically ajusted by the
kernel, but will not exceed specified one, so there is no need to tune
this parameter. Very likely you do not want to change socket queue sizes,
since it may hurt performance, when previously autotuning could rise the
maximum socket buffer size.
--
Evgeniy Polyakov
next prev parent reply other threads:[~2008-10-23 17:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <524f69650810221414n52e236d9rfc6f231d1db75405@mail.gmail.com>
[not found] ` <20081023091325.0ad059c6@barsoom.rdu.redhat.com>
[not found] ` <524f69650810230754m20b815b5n256e82ef1d5dd4f0@mail.gmail.com>
[not found] ` <4a4634330810230926m9285a3etf6340e3de53c576@mail.gmail.com>
2008-10-23 16:42 ` sendmsg blocking with sendtimeout vs. non-blocking Steve French
2008-10-23 17:40 ` Steve French
2008-10-23 17:46 ` Evgeniy Polyakov [this message]
2008-10-23 18:00 ` Jeff Layton
2008-10-23 19:19 ` Steve French
2008-10-23 19:35 ` Jeff Layton
2008-10-23 19:40 ` Steve French
2008-10-23 20:59 ` Evgeniy Polyakov
2008-10-24 1:18 ` Steve French
2008-10-24 1:30 ` Jim Rees
2008-10-24 1:48 ` Jeff Layton
2008-10-24 12:53 ` Neil Horman
2008-10-24 13:59 ` Jim Rees
2008-10-24 15:20 ` Evgeniy Polyakov
2008-10-24 15:36 ` Jim Rees
2008-10-24 15:29 ` Neil Horman
2008-10-24 14:23 ` Steve French
2008-10-24 15:02 ` Shirish Pargaonkar
2008-10-24 16:18 ` Steve French
2008-10-24 1:52 ` Trond Myklebust
2008-10-24 2:06 ` Steve French
2008-10-24 4:43 ` Trond Myklebust
2008-10-23 20:02 ` Jim Rees
2008-10-23 20:18 ` Neil Horman
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=20081023174612.GA14817@2ka.mipt.ru \
--to=zbr@ioremap.net \
--cc=ffilz@us.ibm.com \
--cc=jlayton@redhat.com \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=shirishpargaonkar@gmail.com \
--cc=sjayaraman@suse.de \
--cc=smfrench@gmail.com \
/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.