From: Mike Snitzer <snitzer@kernel.org>
To: Chuck Lever <cel@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-nfs@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [RFC PATCH] NFSD: Add a "file_sync" export option
Date: Thu, 30 Oct 2025 19:39:56 -0400 [thread overview]
Message-ID: <aQP3TCtxGX9bkpGV@kernel.org> (raw)
In-Reply-To: <e86505aa-04d4-49eb-942e-994320d6be1a@kernel.org>
On Thu, Oct 30, 2025 at 03:13:05PM -0400, Chuck Lever wrote:
> On 10/30/25 12:32 PM, Mike Snitzer wrote:
> > On Thu, Oct 30, 2025 at 11:47:15AM -0400, Chuck Lever wrote:
>
> >> But, in the bigger picture, I think comparison between this approach
> >> and NFSD_IO_DIRECT might be illustrative.
> >
> > Sure, I'm very interested in the data myself. A patch to easily
> > enable control is all I'm after. So given what you said above, I'll
> > actually just run with introducing 2 new variants of NFSD_IO_DIRECT
> > for now, so like I mentioned in my previous reply to hch:
> >
> > NFSD_IO_DIRECT_DATA_SYNC
> > NFSD_IO_DIRECT_FILE_SYNC
> >
> > Because it sounds like it is only in the context of NFSD_IO_DIRECT
> > where there is any doubt about whether using NFS_FILE_SYNC helpful.
>
> I'm not sure where you're getting that. FILE_SYNC is interesting for all
> the IO modes, and I'd really like to see specifically the comparison of
> NFSD_IO_BUFFERED with "file_sync" and NFSD_IO_DIRECT with and without
> "file_sync".
I wasn't talking about file_sync being useful or not in general. I
meant based on what you said with file_sync uniformly hurting
performance (even with tmpfs) that it wouldn't be a question for IO
modes other than NFSD_IO_DIRECT.
Anyway, I can change to implementing the control in terms of an export
option.
Mike
prev parent reply other threads:[~2025-10-30 23:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 12:56 [RFC PATCH] NFSD: Add a "file_sync" export option Chuck Lever
2025-10-30 14:20 ` Christoph Hellwig
2025-10-30 15:33 ` Mike Snitzer
2025-10-30 15:45 ` Christoph Hellwig
2025-10-30 16:16 ` Mike Snitzer
2025-10-30 15:47 ` Chuck Lever
2025-10-30 16:32 ` Mike Snitzer
2025-10-30 19:13 ` Chuck Lever
2025-10-30 23:39 ` 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=aQP3TCtxGX9bkpGV@kernel.org \
--to=snitzer@kernel.org \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=hch@infradead.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