From: Chuck Lever <chuck.lever@oracle.com>
To: Christoph Hellwig <hch@infradead.org>, Mike Snitzer <snitzer@kernel.org>
Cc: Jeff Layton <jlayton@kernel.org>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH v4 2/3] NFSD: add new NFSD_IO_DIRECT variants that may override stable_how
Date: Fri, 7 Nov 2025 10:35:52 -0500 [thread overview]
Message-ID: <543c9183-40eb-459b-81bd-078e6ecb7687@oracle.com> (raw)
In-Reply-To: <aQ4RftwuYIxwvLgb@infradead.org>
On 11/7/25 10:34 AM, Christoph Hellwig wrote:
> On Thu, Nov 06, 2025 at 05:56:32PM -0500, Mike Snitzer wrote:
>> OK, I'll take a closer look at NFS client controls for stable_how,
>> because NFSD clearly handles NFS_DATA_SYNC and NFS_FILE_SYNC so I just
>> assumed its because the client does actually send them.
>
> Asking for NFS_DATA_SYNC / NFS_FILE_SYNC for O_ЅYNC/O_SYNC writes or
> even fdatasync/fsync calls that translate to a single on the write write
> request would be a valuable client additoon that should speed things up
> with most if not all servers.
>
>>> And as I said above, "no plan to merge it for now," meaning it's still
>>> on the table for sometime down the road. I have some other ideas I'm
>>> cooking up, such as using BDI congestion to control NFS WRITE
>>> throttling.
>>
>> Hmm, I thought the BDI congestion infra got killed (by Jan Kara and
>> others).. which made me sad because when it was first introduced it
>> was amazing at solving some complex deadlocks (but we're talking 20
>> years ago now). So I haven't kept my finger on the pulse of what is
>> still available to us relative to BDI congestion.
>
> Yes, BDI congestion is gone, mostly because it didn't really work.
> I'm also not sure how it could have solved deadlocks.
>
> I feel a little out of the loops, though - what are the NFS-level
> write throttling needs to start with?
>
Let's not go down this path right now. I'd like to stay focused on
getting the direct WRITE work merged.
--
Chuck Lever
next prev parent reply other threads:[~2025-11-07 15:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 17:42 [PATCH v4 0/3] [PATCH 0/3] NFSD: additional NFSD Direct changes Mike Snitzer
2025-11-05 17:42 ` [PATCH v4 1/3] NFSD: avoid DONTCACHE for misaligned ends of misaligned DIO WRITE Mike Snitzer
2025-11-05 18:47 ` Chuck Lever
2025-11-07 15:29 ` Christoph Hellwig
2025-11-05 17:42 ` [PATCH v4 2/3] NFSD: add new NFSD_IO_DIRECT variants that may override stable_how Mike Snitzer
2025-11-05 18:49 ` Chuck Lever
2025-11-06 20:17 ` Mike Snitzer
2025-11-06 20:35 ` Chuck Lever
2025-11-06 22:56 ` Mike Snitzer
2025-11-07 14:48 ` Chuck Lever
2025-11-07 15:34 ` Christoph Hellwig
2025-11-07 15:35 ` Chuck Lever [this message]
2025-11-07 15:40 ` Christoph Hellwig
2025-11-07 15:30 ` Christoph Hellwig
2025-11-05 17:42 ` [PATCH v4 3/3] NFSD: update Documentation/filesystems/nfs/nfsd-io-modes.rst Mike Snitzer
2025-11-05 18:50 ` 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=543c9183-40eb-459b-81bd-078e6ecb7687@oracle.com \
--to=chuck.lever@oracle.com \
--cc=hch@infradead.org \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=snitzer@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).