From: David Jeffery <djeffery@redhat.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
linux-kernel@vger.kernel.org,
Laurence Oberman <loberman@redhat.com>
Subject: Re: [PATCH] block: recalculate segment count for multi-segment discard requests correctly
Date: Wed, 3 Feb 2021 11:23:37 -0500 [thread overview]
Message-ID: <20210203162337.GA40163@redhat> (raw)
In-Reply-To: <20210203023517.GA948998@T590>
On Wed, Feb 03, 2021 at 10:35:17AM +0800, Ming Lei wrote:
>
> On Tue, Feb 02, 2021 at 03:43:55PM -0500, David Jeffery wrote:
> > The return 0 does seem to be an old relic that does not make sense anymore.
> > Moving REQ_OP_SECURE_ERASE to be with discard and removing the old return 0,
> > is this what you had in mind?
> >
> >
> > diff --git a/block/blk-merge.c b/block/blk-merge.c
> > index 808768f6b174..68458aa01b05 100644
> > --- a/block/blk-merge.c
> > +++ b/block/blk-merge.c
> > @@ -383,8 +383,14 @@ unsigned int blk_recalc_rq_segments(struct request *rq)
> > switch (bio_op(rq->bio)) {
> > case REQ_OP_DISCARD:
> > case REQ_OP_SECURE_ERASE:
> > + if (queue_max_discard_segments(rq->q) > 1) {
> > + struct bio *bio = rq->bio;
> > + for_each_bio(bio)
> > + nr_phys_segs++;
> > + return nr_phys_segs;
> > + }
> > + /* fall through */
> > case REQ_OP_WRITE_ZEROES:
> > - return 0;
> > case REQ_OP_WRITE_SAME:
> > return 1;
>
> WRITE_SAME uses same buffer, so the nr_segment is still one; WRITE_ZERO
> doesn't need extra payload, so nr_segments is zero, see
> blk_bio_write_zeroes_split(), blk_bio_write_same_split, attempt_merge()
> and blk_rq_merge_ok().
>
I thought you mentioned virtio-blk because of how some drivers handle
zeroing and discarding similarly and wanted to align the segment count with
discard behavior for WRITE_ZEROES too. (Though that would also need an update
to blk_bio_write_zeroes_split as you pointed out.) So you want me to leave
WRITE_ZEROES behavior alone and let blk_rq_nr_discard_segments() keep doing
the hiding of a 0 rq->nr_phys_segments as 1 segment in the WRITE_ZEROES treated
as a discard case?
diff --git a/block/blk-merge.c b/block/blk-merge.c
index 808768f6b174..756473295f19 100644
--- a/block/blk-merge.c
+++ b/block/blk-merge.c
@@ -383,6 +383,14 @@ unsigned int blk_recalc_rq_segments(struct request *rq)
switch (bio_op(rq->bio)) {
case REQ_OP_DISCARD:
case REQ_OP_SECURE_ERASE:
+ if (queue_max_discard_segments(rq->q) > 1) {
+ struct bio *bio = rq->bio;
+
+ for_each_bio(bio)
+ nr_phys_segs++;
+ return nr_phys_segs;
+ }
+ return 1;
case REQ_OP_WRITE_ZEROES:
return 0;
case REQ_OP_WRITE_SAME:
--
David Jeffery
next prev parent reply other threads:[~2021-02-03 16:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 16:48 [PATCH] block: recalculate segment count for multi-segment discard requests correctly David Jeffery
2021-02-02 3:33 ` Ming Lei
2021-02-02 20:43 ` David Jeffery
2021-02-03 2:35 ` Ming Lei
2021-02-03 3:15 ` Chaitanya Kulkarni
2021-02-03 13:50 ` Laurence Oberman
2021-02-03 15:08 ` Laurence Oberman
2021-02-03 3:18 ` Chaitanya Kulkarni
2021-02-03 16:23 ` David Jeffery [this message]
2021-02-04 2:18 ` Ming Lei
2021-02-04 2:27 ` Ming Lei
2021-02-04 16:43 ` Laurence Oberman
2021-02-08 18:53 ` Laurence Oberman
2021-02-08 18:58 ` John Pittman
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=20210203162337.GA40163@redhat \
--to=djeffery@redhat.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loberman@redhat.com \
--cc=ming.lei@redhat.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;
as well as URLs for NNTP newsgroup(s).