From: Tom Yan <tom.ty89@gmail.com>
To: linux-block@vger.kernel.org, sergei.shtylyov@gmail.com
Cc: linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org,
Tom Yan <tom.ty89@gmail.com>
Subject: [RFC v2] block: avoid the unnecessary blk_bio_discard_split()
Date: Thu, 10 Dec 2020 19:37:04 +0800 [thread overview]
Message-ID: <20201210113704.1395-1-tom.ty89@gmail.com> (raw)
In-Reply-To: <55e0b8be-a16b-9895-fde5-b325773ae0e7@gmail.com>
It doesn't seem necessary to have the redundant layer of splitting.
The request size will even be more consistent / aligned to the cap.
Signed-off-by: Tom Yan <tom.ty89@gmail.com>
---
block/blk-lib.c | 7 +++++--
block/blk-merge.c | 2 +-
block/blk.h | 8 ++++++--
3 files changed, 12 insertions(+), 5 deletions(-)
diff --git a/block/blk-lib.c b/block/blk-lib.c
index e90614fd8d6a..3b75c1c4ba17 100644
--- a/block/blk-lib.c
+++ b/block/blk-lib.c
@@ -85,12 +85,15 @@ int __blkdev_issue_discard(struct block_device *bdev, sector_t sector,
* is split in device drive, the split ones are very probably
* to be aligned to discard_granularity of the device's queue.
*/
- if (granularity_aligned_lba == sector_mapped)
+ if (granularity_aligned_lba == sector_mapped) {
req_sects = min_t(sector_t, nr_sects,
bio_aligned_discard_max_sectors(q));
- else
+ if (!req_sects)
+ return -EOPNOTSUPP;
+ } else {
req_sects = min_t(sector_t, nr_sects,
granularity_aligned_lba - sector_mapped);
+ }
WARN_ON_ONCE((req_sects << 9) > UINT_MAX);
diff --git a/block/blk-merge.c b/block/blk-merge.c
index 97b7c2821565..f4e030fe6399 100644
--- a/block/blk-merge.c
+++ b/block/blk-merge.c
@@ -59,6 +59,7 @@ static inline bool req_gap_front_merge(struct request *req, struct bio *bio)
return bio_will_gap(req->q, NULL, bio, req->bio);
}
+/* deprecated */
static struct bio *blk_bio_discard_split(struct request_queue *q,
struct bio *bio,
struct bio_set *bs,
@@ -303,7 +304,6 @@ void __blk_queue_split(struct bio **bio, unsigned int *nr_segs)
switch (bio_op(*bio)) {
case REQ_OP_DISCARD:
case REQ_OP_SECURE_ERASE:
- split = blk_bio_discard_split(q, *bio, &q->bio_split, nr_segs);
break;
case REQ_OP_WRITE_ZEROES:
split = blk_bio_write_zeroes_split(q, *bio, &q->bio_split,
diff --git a/block/blk.h b/block/blk.h
index dfab98465db9..e7e31a8c4930 100644
--- a/block/blk.h
+++ b/block/blk.h
@@ -281,8 +281,12 @@ static inline unsigned int bio_allowed_max_sectors(struct request_queue *q)
static inline unsigned int bio_aligned_discard_max_sectors(
struct request_queue *q)
{
- return round_down(UINT_MAX, q->limits.discard_granularity) >>
- SECTOR_SHIFT;
+ unsigned int discard_max_sectors, granularity;
+ discard_max_sectors = min(q->limits.max_discard_sectors,
+ bio_allowed_max_sectors(q));
+ /* Zero-sector (unknown) and one-sector granularities are the same. */
+ granularity = max(q->limits.discard_granularity >> SECTOR_SHIFT, 1U)
+ return round_down(max, granularity);
}
/*
--
2.29.2
next prev parent reply other threads:[~2020-12-10 11:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 6:15 [RFC] block: avoid the unnecessary blk_bio_discard_split() Tom Yan
2020-12-06 10:16 ` Sergei Shtylyov
2020-12-10 11:37 ` Tom Yan [this message]
2020-12-11 16:13 ` [RFC v3] " Tom Yan
2020-12-12 2:01 ` Chaitanya Kulkarni
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=20201210113704.1395-1-tom.ty89@gmail.com \
--to=tom.ty89@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sergei.shtylyov@gmail.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).