From: Christoph Hellwig <hch@infradead.org>
To: Keith Busch <kbusch@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Keith Busch <kbusch@meta.com>,
linux-block@vger.kernel.org, shinichiro.kawasaki@wdc.com
Subject: Re: [PATCH blktests] create a test for direct io offsets
Date: Mon, 20 Oct 2025 22:28:09 -0700 [thread overview]
Message-ID: <aPcZ6ZnAGVwgK1DO@infradead.org> (raw)
In-Reply-To: <aPZhWIokZf0K-Ma9@kbusch-mbp>
On Mon, Oct 20, 2025 at 10:20:40AM -0600, Keith Busch wrote:
> In addition to a flag to say direct-io can use block data split among
> multiple vectors, there's two currently unreported attributes you need
> to know in order to successfuly use direct-io like this: max sectors and
> virtual boundary mask. The max sectors attribute is needed to know
> exactly how many vectors you can insert before the total length needs to
> add up to a block size.
>
> Adding these to statx or fsxattr will help remove a ton of crap from
> this test since I could remove all the stuff extracting it out of sysfs
> from any given file.
Yes. And all the applications would have to do the same things, so this
seems like a huge win. Any chance you could try to get this done ASAP
so that we could make the interface fully discoverable before 6.18 is
released?
next prev parent reply other threads:[~2025-10-21 5:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 20:54 [PATCH blktests] create a test for direct io offsets Keith Busch
2025-10-14 21:21 ` Bart Van Assche
2025-10-14 21:59 ` Keith Busch
2025-10-17 11:13 ` Christoph Hellwig
2025-10-20 16:20 ` Keith Busch
2025-10-21 5:28 ` Christoph Hellwig [this message]
2025-10-21 21:22 ` Keith Busch
2025-10-22 4:46 ` Christoph Hellwig
2025-11-17 21:53 ` Keith Busch
2025-11-18 5:54 ` Christoph Hellwig
2025-10-20 12:40 ` Shinichiro Kawasaki
2025-10-20 21:03 ` Keith Busch
2025-10-21 1:32 ` Shinichiro Kawasaki
2025-10-20 23:25 ` Chaitanya Kulkarni
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=aPcZ6ZnAGVwgK1DO@infradead.org \
--to=hch@infradead.org \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-block@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox