All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@kernel.org>
To: Chuck Lever <cel@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	NeilBrown <neil@brown.name>, 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 v9 05/12] NFSD: Remove alignment size checking
Date: Tue, 4 Nov 2025 10:54:19 -0500	[thread overview]
Message-ID: <aQohqxw9fsqAE2OB@kernel.org> (raw)
In-Reply-To: <35ddc8b0-2727-453e-b970-07b493e21f93@kernel.org>

On Tue, Nov 04, 2025 at 09:14:09AM -0500, Chuck Lever wrote:
> On 11/4/25 6:52 AM, Christoph Hellwig wrote:
> > On Tue, Nov 04, 2025 at 09:30:25AM +1100, NeilBrown wrote:
> >> On Tue, 04 Nov 2025, Chuck Lever wrote:
> >>> From: Chuck Lever <chuck.lever@oracle.com>
> >>>
> >>> Noted that the NFS client's LOCALIO code still retains this check.
> >>
> >> It might be good to capture here *why* the check is removed.
> >> Is it because alignments never exceed PAGE_SIZE, or because the code is
> >> quite capable of handling larger alignments
> >> (I haven't been following the conversation closely..)
> > 
> > I'm still trying to understand why it was added in the first place :)
> 
> I'm trying to understand what action you'd like me to take. Should I
> drop this patch?

Maybe just fold it into Patch 3 and we can forget it ever happened?

The reason it was added is this NFSD_IO_DIRECT feature has had many
iterations, and in the earlier days on its development I was
allocating extra _pages_ to accomodate the misaligned head and tail
pages _outside_ of the sunrpc provided buffers.  This started with
READ and copy-n-paste brought it to the WRITE side IIRC.

> > But I'm also completely lost in the maze of fixup patches.
> Several people have asked me to collapse the fix-ups into a single
> patch. We would lose some history and attributions doing that. Does
> anyone have other thoughts?

The series has a mix of renames that distract, but overall what
matters most is where the code ends up. I don't have a problem with
the various changes when I look at the result (and because I've
acclimated to the evolution). Probably best to just leave well enough
alone given Jeff, myself and Neil have provided various Reviewed-by

Mike

  reply	other threads:[~2025-11-04 15:54 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03 16:53 [PATCH v9 00/12] NFSD: Implement NFSD_IO_DIRECT for NFS WRITE Chuck Lever
2025-11-03 16:53 ` [PATCH v9 01/12] NFSD: Make FILE_SYNC WRITEs comply with spec Chuck Lever
2025-11-03 22:14   ` NeilBrown
2025-11-03 16:53 ` [PATCH v9 02/12] NFSD: Enable return of an updated stable_how to NFS clients Chuck Lever
2025-11-03 16:53 ` [PATCH v9 03/12] NFSD: Implement NFSD_IO_DIRECT for NFS WRITE Chuck Lever
2025-11-06  9:17   ` kernel test robot
2025-11-03 16:53 ` [PATCH v9 04/12] NFSD: Remove specific error handling Chuck Lever
2025-11-03 21:17   ` Mike Snitzer
2025-11-03 16:53 ` [PATCH v9 05/12] NFSD: Remove alignment size checking Chuck Lever
2025-11-03 21:16   ` Mike Snitzer
2025-11-03 22:30   ` NeilBrown
2025-11-04 11:52     ` Christoph Hellwig
2025-11-04 14:14       ` Chuck Lever
2025-11-04 15:54         ` Mike Snitzer [this message]
2025-11-05 12:52         ` Christoph Hellwig
2025-11-05 14:38           ` Chuck Lever
2025-11-05 14:48             ` Mike Snitzer
2025-11-05 14:55             ` Christoph Hellwig
2025-11-03 16:53 ` [PATCH v9 06/12] NFSD: Clean up struct nfsd_write_dio Chuck Lever
2025-11-03 22:36   ` NeilBrown
2025-11-03 16:53 ` [PATCH v9 07/12] NFSD: Introduce struct nfsd_write_dio_seg Chuck Lever
2025-11-03 22:45   ` NeilBrown
2025-11-03 22:48     ` Chuck Lever
2025-11-03 16:53 ` [PATCH v9 08/12] NFSD: Simplify nfsd_iov_iter_aligned_bvec() Chuck Lever
2025-11-03 21:13   ` Mike Snitzer
2025-11-03 22:48   ` NeilBrown
2025-11-03 16:53 ` [PATCH v9 09/12] NFSD: Combine direct I/O feasibility check with iterator setup Chuck Lever
2025-11-03 21:19   ` Mike Snitzer
2025-11-03 22:55   ` NeilBrown
2025-11-03 16:53 ` [PATCH v9 10/12] NFSD: Handle kiocb->ki_flags correctly Chuck Lever
2025-11-03 21:14   ` Mike Snitzer
2025-11-03 23:03   ` NeilBrown
2025-11-04 11:55     ` Christoph Hellwig
2025-11-03 16:53 ` [PATCH v9 11/12] NFSD: Refactor nfsd_vfs_write Chuck Lever
2025-11-03 21:15   ` Mike Snitzer
2025-11-03 23:05   ` NeilBrown
2025-11-03 16:53 ` [PATCH v9 12/12] NFSD: add Documentation/filesystems/nfs/nfsd-io-modes.rst Chuck Lever
2025-11-03 21:25   ` Mike Snitzer

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=aQohqxw9fsqAE2OB@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=neil@brown.name \
    --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.