public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@kernel.org>
To: Anna Schumaker <anna@kernel.org>
Cc: Chuck Lever <cel@kernel.org>,
	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, 30 Mar 2026 14:46:51 -0400	[thread overview]
Message-ID: <acrFG--e2CYhqw0b@kernel.org> (raw)
In-Reply-To: <88adbb3b-38da-4279-a4b8-db68551d6a8b@app.fastmail.com>

On Tue, Mar 17, 2026 at 09:51:23AM -0400, Anna Schumaker wrote:
> 
> 
> On Mon, Mar 16, 2026, at 8:39 AM, Chuck Lever wrote:
> > 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?
> 
> The NFS client would need a code change to support >1MB sizes. I
> spent some time playing around with 4MB yesterday and it passed
> all my tests.

Is this something you'd be open to posting to the list?

Would be interested to see how 'git clone' improves with it.

Thanks,
Mike

      reply	other threads:[~2026-03-30 18:46 UTC|newest]

Thread overview: 6+ 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
2026-03-16 14:40   ` Roland Mainz
2026-03-16 23:35   ` Rick Macklem
2026-03-17 13:51   ` Anna Schumaker
2026-03-30 18:46     ` Mike Snitzer [this message]

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=acrFG--e2CYhqw0b@kernel.org \
    --to=snitzer@kernel.org \
    --cc=anna@kernel.org \
    --cc=cedric.blancher@gmail.com \
    --cc=cel@kernel.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