From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
"Darrick J. Wong" <djwong@kernel.org>,
cem@kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2] xfs: implement XFS_IOC_DIOINFO in terms of vfs_getattr
Date: Wed, 27 Aug 2025 09:36:24 +0200 [thread overview]
Message-ID: <20250827073624.GA24895@lst.de> (raw)
In-Reply-To: <aK3neNcY1vA9lubz@kbusch-mbp>
On Tue, Aug 26, 2025 at 10:57:28AM -0600, Keith Busch wrote:
> Not sure what to say about this patch right now, but it triggered
> a thought: if I can successfully get filesystem and block layers to
> tolerate the hardware's minimum alignments, how is user space to know
> it's allowed to send IO aligned to it? The existing statx dio fields
> just refer to address alignments, but lengths are still assumed to be
> block sized.
Length as in total transfer length? Nothing in the block layer or
storage interface will allow you to do sub-sector transfers, so this
just won't work.
Length as in segment length? If we can support that we'll need a new
limit for that.
next prev parent reply other threads:[~2025-08-27 7:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cG84V92R_rvXt_xDUKDRAZU_E6E69atqXw04uiv_deBLGkFtMFj_XYvumw4sZh6EOFZpn33yItQ55aPJs5hNNw==@protonmail.internalid>
2025-08-25 11:15 ` [PATCH v2] xfs: implement XFS_IOC_DIOINFO in terms of vfs_getattr Christoph Hellwig
2025-08-25 11:32 ` Carlos Maiolino
2025-08-25 11:33 ` Christoph Hellwig
2025-08-25 15:29 ` Darrick J. Wong
2025-08-26 13:14 ` Christoph Hellwig
2025-08-26 16:57 ` Keith Busch
2025-08-27 7:36 ` Christoph Hellwig [this message]
2025-08-28 13:19 ` Carlos Maiolino
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=20250827073624.GA24895@lst.de \
--to=hch@lst.de \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=kbusch@kernel.org \
--cc=linux-xfs@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;
as well as URLs for NNTP newsgroup(s).