All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@kernel.org>
To: NeilBrown <neilb@ownmail.net>
Cc: Chuck Lever <cel@kernel.org>,
	Christoph Hellwig <hch@infradead.org>,
	Jeff Layton <jlayton@kernel.org>,
	Olga Kornievskaia <okorniev@redhat.com>,
	Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
	linux-nfs@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH v11 2/3] NFSD: Implement NFSD_IO_DIRECT for NFS WRITE
Date: Fri, 7 Nov 2025 17:24:18 -0500	[thread overview]
Message-ID: <aQ5xkjIzf6uU_zLa@kernel.org> (raw)
In-Reply-To: <176255273643.634289.15333032218575182744@noble.neil.brown.name>

On Sat, Nov 08, 2025 at 08:58:56AM +1100, NeilBrown wrote:
> On Sat, 08 Nov 2025, Mike Snitzer wrote:
> > On Fri, Nov 07, 2025 at 03:08:11PM -0500, Chuck Lever wrote:
> > > On 11/7/25 3:05 PM, Mike Snitzer wrote:
> > > >> Agreed. The cover letter noted that this is still controversial.
> > > > Only see this, must be missing what you're referring to:
> > > > 
> > > >   Changes since v9:
> > > >   * Unaligned segments no longer use IOCB_DONTCACHE
> > > 
> > > From the v11 cover letter:
> > > 
> > > > One controversy remains: Whether to set DONTCACHE for the unaligned
> > > > segments.
> > 
> > Ha, blind as a bat...
> > 
> > hopefully the rest of my reply helps dispel the controversy
> > 
> 
> Unfortunately I don't think it does.  I don't think it even addresses
> it.
> 
> What Christoph said was:
> 
>    I'd like to sort out the discussion on why to set IOCB_DONTCACHE when
>    nothing is aligned, but not for the non-aligned parts as that is
>    extremely counter-intuitive.
> 
> You gave a lengthy (and probably valid) description on why "not for the
> non-aligned parts" but don't seem to address the "why to set
> IOCB_DONTCACHE when nothing is aligned" bit.

Because if the entire IO is so poorly formed that it cannot be issued
with DIO then at least we can provide the spirit of what was requested
from the admin having cared to enable NFSD_IO_DIRECT.

Those IOs could be quite large.. full WRITE payload.  I have a
reproducer if you'd like it!

Limiting extensive use of caching buffered IO is pretty important if
the admin enabled NFSD_IO_DIRECT.

A misaligned WRITE's non-aligned head and tail are _not_ extensive
amounts of mmeory.  They are at most 2 individial pages.

> I can see Christoph's point.
>
> Can you please explain why all the arguments you have for avoiding
> IOCB_DONTCACHE on the non-aligned head and tail do not equally apply
> when the whole body is assessed as non-aligned.  i.e.  the no_dio label
> in nfsd_write_dio_iters_init().

Sure, hopefully I just did above.

  reply	other threads:[~2025-11-07 22:24 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-07 15:34 [PATCH v11 0/3] NFSD: Implement NFSD_IO_DIRECT for NFS WRITE Chuck Lever
2025-11-07 15:34 ` [PATCH v11 1/3] NFSD: Make FILE_SYNC WRITEs comply with spec Chuck Lever
2025-11-07 15:34 ` [PATCH v11 2/3] NFSD: Implement NFSD_IO_DIRECT for NFS WRITE Chuck Lever
2025-11-07 15:39   ` Christoph Hellwig
2025-11-07 15:40     ` Chuck Lever
2025-11-07 20:05       ` Mike Snitzer
2025-11-07 20:08         ` Chuck Lever
2025-11-07 20:10           ` Mike Snitzer
2025-11-07 21:58             ` NeilBrown
2025-11-07 22:24               ` Mike Snitzer [this message]
2025-11-07 23:42                 ` NeilBrown
2025-11-08  2:01                   ` Mike Snitzer
2025-11-10 16:41                     ` Chuck Lever
2025-11-10 17:57                       ` Mike Snitzer
2025-11-11  8:51                       ` Christoph Hellwig
2025-11-11 14:20                         ` Chuck Lever
2025-11-11 14:21                           ` Christoph Hellwig
2025-11-12  0:06                         ` Mike Snitzer
2025-11-12 15:02                           ` Christoph Hellwig
2025-11-12 23:14                             ` Mike Snitzer
2025-11-13  8:13                               ` Christoph Hellwig
2025-11-13 21:45                                 ` Mike Snitzer
2025-11-07 20:28     ` Chuck Lever
2025-11-07 22:16       ` Mike Snitzer
2025-11-10  9:12         ` Christoph Hellwig
2025-11-10 15:42           ` Mike Snitzer
2025-11-11  8:44             ` Christoph Hellwig
2025-11-10  9:17       ` Christoph Hellwig
2025-11-10 15:43         ` Mike Snitzer
2025-11-07 17:18   ` Mike Snitzer
2025-11-07 22:13   ` NeilBrown
2025-11-07 15:34 ` [PATCH v11 3/3] NFSD: add Documentation/filesystems/nfs/nfsd-io-modes.rst 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=aQ5xkjIzf6uU_zLa@kernel.org \
    --to=snitzer@kernel.org \
    --cc=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=dai.ngo@oracle.com \
    --cc=hch@infradead.org \
    --cc=jlayton@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@ownmail.net \
    --cc=okorniev@redhat.com \
    --cc=tom@talpey.com \
    /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.