From: Jens Axboe <axboe@kernel.dk>
To: linux-block@vger.kernel.org
Cc: osandov@fb.com, efault@gmx.de, paolo.valente@linaro.org,
Jens Axboe <axboe@kernel.dk>
Subject: [PATCH 5/7] bfq-iosched: update shallow depth to smallest one used
Date: Wed, 9 May 2018 14:49:25 -0600 [thread overview]
Message-ID: <1525898967-13425-6-git-send-email-axboe@kernel.dk> (raw)
In-Reply-To: <1525898967-13425-1-git-send-email-axboe@kernel.dk>
If our shallow depth is smaller than the wake batching of sbitmap,
we can introduce hangs. Ensure that sbitmap knows how low we'll go.
Signed-off-by: Jens Axboe <axboe@kernel.dk>
---
block/bfq-iosched.c | 17 ++++++++++++++---
1 file changed, 14 insertions(+), 3 deletions(-)
diff --git a/block/bfq-iosched.c b/block/bfq-iosched.c
index b7722668e295..cba6e82153a2 100644
--- a/block/bfq-iosched.c
+++ b/block/bfq-iosched.c
@@ -5053,10 +5053,13 @@ void bfq_put_async_queues(struct bfq_data *bfqd, struct bfq_group *bfqg)
/*
* See the comments on bfq_limit_depth for the purpose of
- * the depths set in the function.
+ * the depths set in the function. Return minimum shallow depth we'll use.
*/
-static void bfq_update_depths(struct bfq_data *bfqd, struct sbitmap_queue *bt)
+static unsigned int bfq_update_depths(struct bfq_data *bfqd,
+ struct sbitmap_queue *bt)
{
+ unsigned int i, j, min_shallow = UINT_MAX;
+
bfqd->sb_shift = bt->sb.shift;
/*
@@ -5089,14 +5092,22 @@ static void bfq_update_depths(struct bfq_data *bfqd, struct sbitmap_queue *bt)
bfqd->word_depths[1][0] = max(((1U<<bfqd->sb_shift) * 3)>>4, 1U);
/* no more than ~37% of tags for sync writes (~20% extra tags) */
bfqd->word_depths[1][1] = max(((1U<<bfqd->sb_shift) * 6)>>4, 1U);
+
+ for (i = 0; i < 2; i++)
+ for (j = 0; j < 2; j++)
+ min_shallow = min(min_shallow, bfqd->word_depths[i][j]);
+
+ return min_shallow;
}
static int bfq_init_hctx(struct blk_mq_hw_ctx *hctx, unsigned int index)
{
struct bfq_data *bfqd = hctx->queue->elevator->elevator_data;
struct blk_mq_tags *tags = hctx->sched_tags;
+ unsigned int min_shallow;
- bfq_update_depths(bfqd, &tags->bitmap_tags);
+ min_shallow = bfq_update_depths(bfqd, &tags->bitmap_tags);
+ sbitmap_queue_shallow_depth(&tags->bitmap_tags, min_shallow);
return 0;
}
--
2.7.4
next prev parent reply other threads:[~2018-05-09 20:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 20:49 [PATCHSET v2 0/7] blk-mq-sched and sbitmap shallow depth Jens Axboe
2018-05-09 20:49 ` [PATCH 1/7] blk-mq: don't call into depth limiting for reserved tags Jens Axboe
2018-05-09 20:49 ` [PATCH 2/7] bfq-iosched: don't worry about reserved tags in limit_depth Jens Axboe
2018-05-09 20:49 ` [PATCH 3/7] bfq: calculate shallow depths at init time Jens Axboe
2018-05-09 20:49 ` [PATCH 4/7] sbitmap: add helper to inform the core about shallow depth limiting Jens Axboe
2018-05-09 20:49 ` Jens Axboe [this message]
2018-05-09 20:49 ` [PATCH 6/7] bfq-iosched: remove unused variable Jens Axboe
2018-05-09 20:49 ` [PATCH 7/7] kyber-iosched: update shallow depth when setting up hardware queue Jens Axboe
2018-05-10 4:32 ` [PATCHSET v2 0/7] blk-mq-sched and sbitmap shallow depth Paolo Valente
2018-05-10 16:20 ` Jens Axboe
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=1525898967-13425-6-git-send-email-axboe@kernel.dk \
--to=axboe@kernel.dk \
--cc=efault@gmx.de \
--cc=linux-block@vger.kernel.org \
--cc=osandov@fb.com \
--cc=paolo.valente@linaro.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).