From: "Darrick J. Wong" <djwong@kernel.org>
To: Brian Foster <bfoster@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH v2 01/12] iomap: advance the iter directly on buffered read
Date: Wed, 19 Feb 2025 14:31:44 -0800 [thread overview]
Message-ID: <20250219223144.GH21808@frogsfrogsfrogs> (raw)
In-Reply-To: <20250219222235.GB21808@frogsfrogsfrogs>
On Wed, Feb 19, 2025 at 02:22:35PM -0800, Darrick J. Wong wrote:
> On Wed, Feb 19, 2025 at 12:50:39PM -0500, Brian Foster wrote:
> > iomap buffered read advances the iter via iter.processed. To
> > continue separating iter advance from return status, update
> > iomap_readpage_iter() to advance the iter instead of returning the
> > number of bytes processed. In turn, drop the offset parameter and
> > sample the updated iter->pos at the start of the function. Update
> > the callers to loop based on remaining length in the current
> > iteration instead of number of bytes processed.
> >
> > Signed-off-by: Brian Foster <bfoster@redhat.com>
> > Reviewed-by: Christoph Hellwig <hch@lst.de>
> > ---
> > fs/iomap/buffered-io.c | 45 +++++++++++++++++++-----------------------
> > 1 file changed, 20 insertions(+), 25 deletions(-)
> >
> > diff --git a/fs/iomap/buffered-io.c b/fs/iomap/buffered-io.c
> > index ec227b45f3aa..215866ba264d 100644
> > --- a/fs/iomap/buffered-io.c
> > +++ b/fs/iomap/buffered-io.c
> > @@ -366,15 +366,14 @@ static inline bool iomap_block_needs_zeroing(const struct iomap_iter *iter,
> > pos >= i_size_read(iter->inode);
> > }
> >
> > -static loff_t iomap_readpage_iter(const struct iomap_iter *iter,
> > - struct iomap_readpage_ctx *ctx, loff_t offset)
> > +static loff_t iomap_readpage_iter(struct iomap_iter *iter,
>
> I wonder, do we really need to return loff_t from some of these
> functions now? I thought the only return codes were the -EIO/0 from
> iomap_iter_advance?
And that's provided in the last patch so
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
>
> --D
>
> > + struct iomap_readpage_ctx *ctx)
> > {
> > const struct iomap *iomap = &iter->iomap;
> > - loff_t pos = iter->pos + offset;
> > - loff_t length = iomap_length(iter) - offset;
> > + loff_t pos = iter->pos;
> > + loff_t length = iomap_length(iter);
> > struct folio *folio = ctx->cur_folio;
> > struct iomap_folio_state *ifs;
> > - loff_t orig_pos = pos;
> > size_t poff, plen;
> > sector_t sector;
> >
> > @@ -438,25 +437,22 @@ static loff_t iomap_readpage_iter(const struct iomap_iter *iter,
> > * we can skip trailing ones as they will be handled in the next
> > * iteration.
> > */
> > - return pos - orig_pos + plen;
> > + length = pos - iter->pos + plen;
> > + return iomap_iter_advance(iter, &length);
> > }
> >
> > -static loff_t iomap_read_folio_iter(const struct iomap_iter *iter,
> > +static loff_t iomap_read_folio_iter(struct iomap_iter *iter,
> > struct iomap_readpage_ctx *ctx)
> > {
> > - struct folio *folio = ctx->cur_folio;
> > - size_t offset = offset_in_folio(folio, iter->pos);
> > - loff_t length = min_t(loff_t, folio_size(folio) - offset,
> > - iomap_length(iter));
> > - loff_t done, ret;
> > -
> > - for (done = 0; done < length; done += ret) {
> > - ret = iomap_readpage_iter(iter, ctx, done);
> > - if (ret <= 0)
> > + loff_t ret;
> > +
> > + while (iomap_length(iter)) {
> > + ret = iomap_readpage_iter(iter, ctx);
> > + if (ret)
> > return ret;
> > }
> >
> > - return done;
> > + return 0;
> > }
> >
> > int iomap_read_folio(struct folio *folio, const struct iomap_ops *ops)
> > @@ -493,15 +489,14 @@ int iomap_read_folio(struct folio *folio, const struct iomap_ops *ops)
> > }
> > EXPORT_SYMBOL_GPL(iomap_read_folio);
> >
> > -static loff_t iomap_readahead_iter(const struct iomap_iter *iter,
> > +static loff_t iomap_readahead_iter(struct iomap_iter *iter,
> > struct iomap_readpage_ctx *ctx)
> > {
> > - loff_t length = iomap_length(iter);
> > - loff_t done, ret;
> > + loff_t ret;
> >
> > - for (done = 0; done < length; done += ret) {
> > + while (iomap_length(iter)) {
> > if (ctx->cur_folio &&
> > - offset_in_folio(ctx->cur_folio, iter->pos + done) == 0) {
> > + offset_in_folio(ctx->cur_folio, iter->pos) == 0) {
> > if (!ctx->cur_folio_in_bio)
> > folio_unlock(ctx->cur_folio);
> > ctx->cur_folio = NULL;
> > @@ -510,12 +505,12 @@ static loff_t iomap_readahead_iter(const struct iomap_iter *iter,
> > ctx->cur_folio = readahead_folio(ctx->rac);
> > ctx->cur_folio_in_bio = false;
> > }
> > - ret = iomap_readpage_iter(iter, ctx, done);
> > - if (ret <= 0)
> > + ret = iomap_readpage_iter(iter, ctx);
> > + if (ret)
> > return ret;
> > }
> >
> > - return done;
> > + return 0;
> > }
> >
> > /**
> > --
> > 2.48.1
> >
> >
>
next prev parent reply other threads:[~2025-02-19 22:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 17:50 [PATCH v2 00/12] iomap: incremental advance conversion -- phase 2 Brian Foster
2025-02-19 17:50 ` [PATCH v2 01/12] iomap: advance the iter directly on buffered read Brian Foster
2025-02-19 22:22 ` Darrick J. Wong
2025-02-19 22:31 ` Darrick J. Wong [this message]
2025-02-19 17:50 ` [PATCH v2 02/12] iomap: advance the iter on direct I/O Brian Foster
2025-02-19 22:22 ` Darrick J. Wong
2025-02-19 17:50 ` [PATCH v2 03/12] iomap: convert misc simple ops to incremental advance Brian Foster
2025-02-19 22:24 ` Darrick J. Wong
2025-02-19 22:31 ` Darrick J. Wong
2025-02-19 17:50 ` [PATCH v2 04/12] dax: advance the iomap_iter in the read/write path Brian Foster
2025-02-19 22:33 ` Darrick J. Wong
2025-02-20 14:58 ` Brian Foster
2025-02-19 17:50 ` [PATCH v2 05/12] dax: push advance down into dax_iomap_iter() for read and write Brian Foster
2025-02-19 22:34 ` Darrick J. Wong
2025-02-19 17:50 ` [PATCH v2 06/12] dax: advance the iomap_iter on zero range Brian Foster
2025-02-19 22:34 ` Darrick J. Wong
2025-02-19 17:50 ` [PATCH v2 07/12] dax: advance the iomap_iter on unshare range Brian Foster
2025-02-19 22:35 ` Darrick J. Wong
2025-02-19 17:50 ` [PATCH v2 08/12] dax: advance the iomap_iter on dedupe range Brian Foster
2025-02-19 22:35 ` Darrick J. Wong
2025-02-19 17:50 ` [PATCH v2 09/12] dax: advance the iomap_iter on pte and pmd faults Brian Foster
2025-02-19 22:36 ` Darrick J. Wong
2025-02-19 17:50 ` [PATCH v2 10/12] iomap: remove unnecessary advance from iomap_iter() Brian Foster
2025-02-19 22:30 ` Darrick J. Wong
2025-02-19 17:50 ` [PATCH v2 11/12] iomap: rename iomap_iter processed field to status Brian Foster
2025-02-19 22:30 ` Darrick J. Wong
2025-02-19 17:50 ` [PATCH v2 12/12] iomap: introduce a full map advance helper Brian Foster
2025-02-19 22:31 ` Darrick J. Wong
2025-02-20 9:10 ` [PATCH v2 00/12] iomap: incremental advance conversion -- phase 2 Christian Brauner
2025-02-20 14:59 ` Brian Foster
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=20250219223144.GH21808@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=bfoster@redhat.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.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).