From: Christoph Hellwig <hch@lst.de>
To: changfengnan@bytedance.com, Joanne Koong <joannelkoong@gmail.com>,
"Darrick J. Wong" <djwong@kernel.org>,
Christian Brauner <brauner@kernel.org>
Cc: "Theodore Ts'o" <tytso@mit.edu>, Carlos Maiolino <cem@kernel.org>,
linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: decouple simple direct I/O reads from iomap_dio_rw v2
Date: Thu, 23 Jul 2026 07:01:38 +0200 [thread overview]
Message-ID: <20260723050201.3381045-1-hch@lst.de> (raw)
Hi all,
this series reworks how the iomap simple dio read fast path is called and
decouples it from the generic iomap_dio_rw and the iomap iter. This is
to make the iomap_iter_next transition easier and cleaner. It slots in
after the first patch from Joanne's
[PATCH v3 00/20] iomap: convert to in-iter iomap_next() model
series, and the first patch from that is included as the first patch
here unmodified as reference. If the approach looks good to everyone,
I'd suggest to include it in the next spin of that series.
Changes since v1:
- fix i_dio_count on synchronous errors
- use read in the name also for the __-helper
next reply other threads:[~2026-07-23 5:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 5:01 Christoph Hellwig [this message]
2026-07-23 5:01 ` [PATCH 1/3] iomap: split iomap_iter() logic into iomap_iter_next() Christoph Hellwig
2026-07-23 5:01 ` [PATCH 2/3] iomap: decouple simple direct I/O reads from iomap_dio_rw Christoph Hellwig
2026-07-23 5:01 ` [PATCH 3/3] iomap: use GFP_NOWAIT when application for iomap_dio_simple allocations Christoph Hellwig
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=20260723050201.3381045-1-hch@lst.de \
--to=hch@lst.de \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=changfengnan@bytedance.com \
--cc=djwong@kernel.org \
--cc=joannelkoong@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=tytso@mit.edu \
/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