From: Christoph Hellwig <hch@infradead.org>
To: NeilBrown <neil@brown.name>
Cc: Ameer Hamza <ameer.hamza@truenas.com>,
cel@kernel.org, jlayton@kernel.org, okorniev@redhat.com,
Dai.Ngo@oracle.com, tom@talpey.com, trondmy@kernel.org,
anna@kernel.org, linux-nfs@vger.kernel.org,
linux-kernel@vger.kernel.org, alexander.motin@truenas.com,
caleb.stjohn@truenas.com
Subject: Re: [PATCH 1/2] NFSD: Use nfsd_iter_read() when ->splice_read is not zero-copy
Date: Tue, 18 Aug 2026 22:59:31 -0700 [thread overview]
Message-ID: <aoVGQ5a7ZhMmq2xY@infradead.org> (raw)
In-Reply-To: <178709365192.2852630.5607658976022815566@noble.neil.brown.name>
On Wed, Aug 19, 2026 at 08:54:11AM +1000, NeilBrown wrote:
> I think that if we are going to do this then we should do it properly
> and make it easy to detect these cases.
That's a big IFF. The splice fallback is a generate case. And no,
we should not add flags and big blobs of NFSD code to work around it,
there's simply no point in optimizing for some LLM generated ext4 on
fake DAX bullshit.
next prev parent reply other threads:[~2026-08-19 5:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 21:08 [PATCH 0/2] SUNRPC: Recycle sent Reply pages instead of freeing them Ameer Hamza
2026-08-17 21:08 ` [PATCH 1/2] NFSD: Use nfsd_iter_read() when ->splice_read is not zero-copy Ameer Hamza
2026-08-18 13:55 ` Chuck Lever
2026-08-18 23:12 ` Ameer Hamza
2026-08-18 14:42 ` Christoph Hellwig
2026-08-18 23:44 ` Ameer Hamza
2026-08-18 22:54 ` NeilBrown
2026-08-18 23:22 ` Ameer Hamza
2026-08-19 5:59 ` Christoph Hellwig [this message]
2026-08-17 21:08 ` [PATCH 2/2] SUNRPC: Recycle sent Reply pages instead of freeing them Ameer Hamza
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=aoVGQ5a7ZhMmq2xY@infradead.org \
--to=hch@infradead.org \
--cc=Dai.Ngo@oracle.com \
--cc=alexander.motin@truenas.com \
--cc=ameer.hamza@truenas.com \
--cc=anna@kernel.org \
--cc=caleb.stjohn@truenas.com \
--cc=cel@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=tom@talpey.com \
--cc=trondmy@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.