From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>, Carlos Maiolino <cem@kernel.org>,
Damien Le Moal <dlemoal@kernel.org>,
Hans Holmberg <hans.holmberg@wdc.com>,
linux-block@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/3] block: add a bio_reuse helper
Date: Fri, 9 Jan 2026 16:50:09 -0800 [thread overview]
Message-ID: <20260110005009.GU15551@frogsfrogsfrogs> (raw)
In-Reply-To: <20260109162506.GA16090@lst.de>
On Fri, Jan 09, 2026 at 05:25:06PM +0100, Christoph Hellwig wrote:
> On Fri, Jan 09, 2026 at 08:19:06AM -0800, Darrick J. Wong wrote:
> > General question about bio_reset -- it calls bio_uninit, which strips
> > off the integrity and crypt metadata. I /think/ that will all get
> > re-added if necessary during the subsequent bio submission, right?
>
> Yes.
>
> > For your zonegc case, I wonder if it's actually a good idea to keep that
> > metadata attached as long as the bdev doesn't change across reuse?
>
> We need to generate different metadata for a different block location.
> Reusing the allocation might be useful, but it would really complicate
> this API, especially as the currently most common way to use integrity
> metadata is through the block layer auto PI, which allocates it below
> submit_bio and frees it before calling back into the submitter on I/O
> completion.
>
> But it might be worth writing up another sentence on this in the comment.
Yes, please. :)
With that brief mention that PI/crypt data get regenerated, I think I
understand what this (fairly brief refactoring) does, so
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
next prev parent reply other threads:[~2026-01-10 0:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 7:58 improve zoned XFS GC buffer management v2 Christoph Hellwig
2026-01-06 7:58 ` [PATCH 1/3] block: add a bio_reuse helper Christoph Hellwig
2026-01-09 12:12 ` Carlos Maiolino
2026-01-09 16:19 ` Darrick J. Wong
2026-01-09 16:25 ` Christoph Hellwig
2026-01-10 0:50 ` Darrick J. Wong [this message]
2026-01-09 16:30 ` Carlos Maiolino
2026-01-12 20:22 ` Jens Axboe
2026-01-06 7:58 ` [PATCH 2/3] xfs: use bio_reuse in the zone GC code Christoph Hellwig
2026-01-09 12:13 ` Carlos Maiolino
2026-01-06 7:58 ` [PATCH 3/3] xfs: rework zone GC buffer management Christoph Hellwig
2026-01-09 12:24 ` Carlos Maiolino
2026-01-09 15:03 ` improve zoned XFS GC buffer management v2 Carlos Maiolino
-- strict thread matches above, loose matches on Subject: below --
2026-01-14 13:06 improve zoned XFS GC buffer management v4 Christoph Hellwig
2026-01-14 13:06 ` [PATCH 1/3] block: add a bio_reuse helper Christoph Hellwig
2026-01-13 7:19 improve zoned XFS GC buffer management v3 Christoph Hellwig
2026-01-13 7:19 ` [PATCH 1/3] block: add a bio_reuse helper Christoph Hellwig
2025-12-18 6:31 improve zoned XFS GC buffer management Christoph Hellwig
2025-12-18 6:31 ` [PATCH 1/3] block: add a bio_reuse helper Christoph Hellwig
2025-12-18 6:43 ` Damien Le Moal
2025-12-18 9:20 ` Hannes Reinecke
2025-12-18 9:35 ` Christoph Hellwig
2025-12-18 9:40 ` Ming Lei
2025-12-18 9:45 ` Christoph Hellwig
2025-12-19 7:45 ` Hans Holmberg
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=20260110005009.GU15551@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=axboe@kernel.dk \
--cc=cem@kernel.org \
--cc=dlemoal@kernel.org \
--cc=hans.holmberg@wdc.com \
--cc=hch@lst.de \
--cc=linux-block@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