From: "J. Bruce Fields" <bfields@fieldses.org>
To: James Vanns <james.vanns@framestore.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Where in the server code is fsinfo rtpref calculated?
Date: Tue, 14 May 2013 18:01:22 -0400 [thread overview]
Message-ID: <20130514220122.GE16811@fieldses.org> (raw)
In-Reply-To: <433790995.19587230.1368530229981.JavaMail.root@framestore.com>
On Tue, May 14, 2013 at 12:17:10PM +0100, James Vanns wrote:
> Hi. I'm struggling to locate the region in the NFSv3 server-side code
> where it figures out the block sizes for the FSINFO reply. We have
> servers that do not specify r/wsizes in their exports
There's no way to specify that as an export option. You can configure
it server-wide using /proc/fs/nfsd/max_block_size.
> and so I need to
> find where this negotiated value between server->client actually comes
> from. How does the server reach the preferred block size for a given
> export?
fs/nfsd/nfssvc.c:nfsd_get_default_maxblksize() is probably a good
starting point. Its caller, nfsd_create_serv(), calls
svc_create_pooled() with the result that's calculated.
For fsinfo see fs/nfsd/nfs3proc.c:nfsd3_proc_fsinfo, which uses
svc_max_payload().
--b.
next prev parent reply other threads:[~2013-05-14 22:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 11:17 Where in the server code is fsinfo rtpref calculated? James Vanns
2013-05-14 22:01 ` J. Bruce Fields [this message]
2013-05-15 9:21 ` James Vanns
2013-05-15 13:42 ` James Vanns
2013-05-15 14:15 ` J. Bruce Fields
2013-05-15 14:34 ` James Vanns
2013-05-15 14:47 ` J. Bruce Fields
2013-05-15 15:20 ` Myklebust, Trond
2013-05-15 16:32 ` James Vanns
2013-05-15 17:42 ` J. Bruce Fields
2013-05-17 11:43 ` James Vanns
2013-05-17 13:56 ` J. Bruce Fields
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=20130514220122.GE16811@fieldses.org \
--to=bfields@fieldses.org \
--cc=james.vanns@framestore.com \
--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;
as well as URLs for NNTP newsgroup(s).