From: Keith Busch <kbusch@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Keith Busch <kbusch@meta.com>,
linux-block@vger.kernel.org, axboe@kernel.dk
Subject: Re: [PATCHv2] blk-mq: set the nr_integrity_segments from bio
Date: Wed, 4 Sep 2024 08:47:51 -0600 [thread overview]
Message-ID: <ZthzF5Go69cdzeoM@kbusch-mbp> (raw)
In-Reply-To: <Ztfjb8UlOfHYtMTT@infradead.org>
On Tue, Sep 03, 2024 at 09:34:55PM -0700, Christoph Hellwig wrote:
> On Tue, Sep 03, 2024 at 12:13:25PM -0700, Keith Busch wrote:
> > --- a/block/blk-mq.c
> > +++ b/block/blk-mq.c
> > @@ -2546,6 +2546,10 @@ static void blk_mq_bio_to_request(struct request *rq, struct bio *bio,
> > rq->__sector = bio->bi_iter.bi_sector;
> > rq->write_hint = bio->bi_write_hint;
> > blk_rq_bio_prep(rq, bio, nr_segs);
> > +#if defined(CONFIG_BLK_DEV_INTEGRITY)
> > + if (bio->bi_opf & REQ_INTEGRITY)
> > + rq->nr_integrity_segments = blk_rq_count_integrity_sg(rq->q, bio);
>
> Hmm. The current model is that drivers are supposed to
> clal this, which they should stop doing now that the block layer
> maintains this count. So I think this needs a bit more work, after
> which blk_rq_count_integrity_sg is also unexported, nad preferably
> also has a name that drops the incorrect _sg.
Sure, I have a larger patch set in the works doing pretty much that.
I wanted the request's existing field to be accurate first because
inaccurate values break merging. But I can post the rest of series if
you prefer to see drivers rely on the existing field instead of
recounting the segments.
prev parent reply other threads:[~2024-09-04 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 19:13 [PATCHv2] blk-mq: set the nr_integrity_segments from bio Keith Busch
2024-09-04 4:34 ` Christoph Hellwig
2024-09-04 14:47 ` Keith Busch [this message]
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=ZthzF5Go69cdzeoM@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=kbusch@meta.com \
--cc=linux-block@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).