From: "Chuck Lever" <cel@kernel.org>
To: "Cedric Blancher" <cedric.blancher@gmail.com>,
"Linux NFS Mailing List" <linux-nfs@vger.kernel.org>
Subject: Re: Increase default NFSv4 server size "max_block_size" to 4MB
Date: Mon, 16 Mar 2026 08:39:26 -0400 [thread overview]
Message-ID: <5acaa8e7-0691-4cbd-b501-c26831a7be81@app.fastmail.com> (raw)
In-Reply-To: <CALXu0UdOR8mVr=8pwNP95FnOsOk1w1A2=DcayKk3YnDfS+PzUA@mail.gmail.com>
On Mon, Mar 16, 2026, at 3:51 AM, Cedric Blancher wrote:
> As debated a while ago, can the default NFSv4 server size for
> "max_block_size" be increased to 4MB, please?
There is an administrative setting to raise this limit for
recent versions of the kernel. Can you report your experience
when you raise the limit? Hiccups, performance issues, etc? I
would kind of like this exercise to be data-driven.
What is still unknown to me is which NFS client implementations
can support 4MB or 8MB. Without client support, an increase in
the default in NFSD doesn't mean anything. Rick, Anna, Roland?
--
Chuck Lever
next prev parent reply other threads:[~2026-03-16 12:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 7:51 Increase default NFSv4 server size "max_block_size" to 4MB Cedric Blancher
2026-03-16 12:39 ` Chuck Lever [this message]
2026-03-16 14:40 ` Roland Mainz
2026-03-16 23:35 ` Rick Macklem
2026-05-12 13:18 ` Increase FreeBSD NFSv4 nfsd buffer size? " Cedric Blancher
2026-05-12 23:02 ` Rick Macklem
2026-05-13 8:37 ` Cedric Blancher
2026-05-13 23:38 ` Rick Macklem
2026-05-14 22:39 ` Rick Macklem
2026-05-14 22:52 ` vermaden
2026-05-14 23:49 ` Rick Macklem
2026-03-17 13:51 ` Anna Schumaker
2026-03-30 18:46 ` Mike Snitzer
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=5acaa8e7-0691-4cbd-b501-c26831a7be81@app.fastmail.com \
--to=cel@kernel.org \
--cc=cedric.blancher@gmail.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 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.