From: Jeff Layton <jlayton@kernel.org>
To: Mike Snitzer <snitzer@kernel.org>, Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2 4/4] NFSD: handle unaligned DIO for NFS reexport
Date: Thu, 31 Jul 2025 16:58:00 -0400 [thread overview]
Message-ID: <b5e2e433e70189b4ed05417f8bdb2ff98a82881e.camel@kernel.org> (raw)
In-Reply-To: <20250731194448.88816-5-snitzer@kernel.org>
On Thu, 2025-07-31 at 15:44 -0400, Mike Snitzer wrote:
> NFS doesn't have any DIO alignment constraints but it doesn't support
> STATX_DIOALIGN, so update NFSD such that it doesn't disable the use of
> NFSD_IO_DIRECT if it is reexporting NFS.
>
> Signed-off-by: Mike Snitzer <snitzer@kernel.org>
> ---
> fs/nfs/export.c | 3 ++-
> fs/nfsd/filecache.c | 11 +++++++++++
> include/linux/exportfs.h | 13 +++++++++++++
> 3 files changed, 26 insertions(+), 1 deletion(-)
>
> diff --git a/fs/nfs/export.c b/fs/nfs/export.c
> index e9c233b6fd209..2cae75ba6b35d 100644
> --- a/fs/nfs/export.c
> +++ b/fs/nfs/export.c
> @@ -155,5 +155,6 @@ const struct export_operations nfs_export_ops = {
> EXPORT_OP_REMOTE_FS |
> EXPORT_OP_NOATOMIC_ATTR |
> EXPORT_OP_FLUSH_ON_CLOSE |
> - EXPORT_OP_NOLOCKS,
> + EXPORT_OP_NOLOCKS |
> + EXPORT_OP_NO_DIOALIGN_NEEDED,
> };
> diff --git a/fs/nfsd/filecache.c b/fs/nfsd/filecache.c
> index 5601e839a72da..ea489dd44fd9a 100644
> --- a/fs/nfsd/filecache.c
> +++ b/fs/nfsd/filecache.c
> @@ -1066,6 +1066,17 @@ nfsd_file_getattr(const struct svc_fh *fhp, struct nfsd_file *nf)
> nfsd_io_cache_write != NFSD_IO_DIRECT))
> return nfs_ok;
>
> + if (exportfs_handles_unaligned_dio(nf->nf_file->f_path.mnt->mnt_sb->s_export_op)) {
> + /* Underlying filesystem doesn't support STATX_DIOALIGN
> + * but it can handle all unaligned DIO, so establish
> + * DIO alignment that is accommodating.
> + */
> + nf->nf_dio_mem_align = 4;
> + nf->nf_dio_offset_align = PAGE_SIZE;
> + nf->nf_dio_read_offset_align = nf->nf_dio_offset_align;
> + return nfs_ok;
> + }
> +
> status = fh_getattr(fhp, &stat);
> if (status != nfs_ok)
> return status;
> diff --git a/include/linux/exportfs.h b/include/linux/exportfs.h
> index 9369a607224c1..626b8486dd985 100644
> --- a/include/linux/exportfs.h
> +++ b/include/linux/exportfs.h
> @@ -247,6 +247,7 @@ struct export_operations {
> */
> #define EXPORT_OP_FLUSH_ON_CLOSE (0x20) /* fs flushes file data on close */
> #define EXPORT_OP_NOLOCKS (0x40) /* no file locking support */
> +#define EXPORT_OP_NO_DIOALIGN_NEEDED (0x80) /* fs can handle unaligned DIO */
> unsigned long flags;
> };
>
> @@ -262,6 +263,18 @@ exportfs_cannot_lock(const struct export_operations *export_ops)
> return export_ops->flags & EXPORT_OP_NOLOCKS;
> }
>
> +/**
> + * exportfs_handles_unaligned_dio() - check if export can handle unaligned DIO
> + * @export_ops: the nfs export operations to check
> + *
> + * Returns true if the export can handle unaligned DIO.
> + */
> +static inline bool
> +exportfs_handles_unaligned_dio(const struct export_operations *export_ops)
> +{
> + return export_ops->flags & EXPORT_OP_NO_DIOALIGN_NEEDED;
> +}
> +
> extern int exportfs_encode_inode_fh(struct inode *inode, struct fid *fid,
> int *max_len, struct inode *parent,
> int flags);
Would it not be simpler (better?) to add support for STATX_DIOALIGN to
NFS, and just have it report '1' for both values?
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2025-07-31 20:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 19:44 [PATCH v2 0/4] NFSD DIRECT: add handling for misaligned WRITEs Mike Snitzer
2025-07-31 19:44 ` [PATCH v2 1/4] NFSD: refactor nfsd_read_vector_dio to EVENT_CLASS useful for READ and WRITE Mike Snitzer
2025-07-31 20:28 ` Jeff Layton
2025-07-31 19:44 ` [PATCH v2 2/4] NFSD: prepare nfsd_vfs_write() to use O_DIRECT on misaligned WRITEs Mike Snitzer
2025-07-31 20:28 ` Jeff Layton
2025-07-31 20:49 ` Mike Snitzer
2025-07-31 20:54 ` Jeff Layton
2025-07-31 19:44 ` [PATCH v2 3/4] NFSD: issue WRITEs using O_DIRECT even if IO is misaligned Mike Snitzer
2025-07-31 20:53 ` Jeff Layton
2025-07-31 19:44 ` [PATCH v2 4/4] NFSD: handle unaligned DIO for NFS reexport Mike Snitzer
2025-07-31 20:58 ` Jeff Layton [this message]
2025-07-31 21:28 ` Mike Snitzer
2025-07-31 21:45 ` Jeff Layton
2025-07-31 22:14 ` Mike Snitzer
2025-08-01 23:17 ` Tom Talpey
2025-07-31 21:48 ` Mike Snitzer
2025-08-01 14:07 ` Chuck Lever
2025-08-01 14:33 ` Jeff Layton
2025-08-01 16:06 ` 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=b5e2e433e70189b4ed05417f8bdb2ff98a82881e.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=chuck.lever@oracle.com \
--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).