From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: James Pearson
<james-p-5Ol4pYTxKWu0ML75eksnrtBPR1lH4CV8@public.gmane.org>
Cc: Chuck Lever <chuck.lever@oracle.com>, linux-nfs@vger.kernel.org
Subject: Re: Text based mount options ignoring the preferred rwsize?
Date: Wed, 09 Sep 2009 18:56:10 -0400 [thread overview]
Message-ID: <1252536970.8722.110.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <4AA8225A.9060107-5Ol4pYTxKWu0ML75eksnrtBPR1lH4CV8@public.gmane.org>
On Wed, 2009-09-09 at 22:47 +0100, James Pearson wrote:
> The default behaviour with binary mount options when no [rw]size is to
> select these preferred values - which to me, makes sense - as by not
> giving a [rw]size, you are leaving it up the server to pick the 'best'
> values for you - which I guess in most (all other?) cases happen to be
> the maximum size.
Right. The above was indeed the guiding principle back when I did the
rsize/wsize negotiation for NFSv3 and NFSv2 for the binary mount code.
The NFS protocol specifies that the maximum values are there to tell you
that the server will do short read/writes if you exceed these. However,
the preferred values may correspond to a different 'sweet spot' for the
server read and write implementations.
Cheers
Trond
next prev parent reply other threads:[~2009-09-09 22:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 16:47 Text based mount options ignoring the preferred rwsize? James Pearson
[not found] ` <4AA68AA4.7090606-5Ol4pYTxKWu0ML75eksnrtBPR1lH4CV8@public.gmane.org>
2009-09-09 19:23 ` Chuck Lever
2009-09-09 21:47 ` James Pearson
[not found] ` <4AA8225A.9060107-5Ol4pYTxKWu0ML75eksnrtBPR1lH4CV8@public.gmane.org>
2009-09-09 22:34 ` Chuck Lever
2009-09-09 22:56 ` Trond Myklebust [this message]
[not found] ` <1252536970.8722.110.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-09-10 9:08 ` James Pearson
[not found] ` <4AA8C215.2030002-5Ol4pYTxKWu0ML75eksnrtBPR1lH4CV8@public.gmane.org>
2009-09-10 17:49 ` Chuck Lever
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=1252536970.8722.110.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=chuck.lever@oracle.com \
--cc=james-p-5Ol4pYTxKWu0ML75eksnrtBPR1lH4CV8@public.gmane.org \
--cc=linux-nfs@vger.kernel.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