From: Jens Axboe <axboe@kernel.dk>
To: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: [PATCH] blk-wbt: fix indefinite background writeback sleep
Date: Fri, 22 Jun 2018 13:26:10 -0600 [thread overview]
Message-ID: <0fa9cc9f-7d34-2490-cdaf-fe7a761e4790@kernel.dk> (raw)
blk-wbt adds waiters to the tail of the waitqueue, and factors in the
task placement in its decision making on whether or not the current task
can proceed. This can cause issues for the lowest class of writers,
since they can get woken up, denied access, and then put back to sleep
at the end of the waitqueue.
Fix this so that we only utilize the tail add for the initial sleep, and
we don't factor in the wait queue placement after we've slept (and are
now using the head addition).
Fixes: e34cbd307477 ("blk-wbt: add general throttling mechanism")
Signed-off-by: Jens Axboe <axboe@kernel.dk>
diff --git a/block/blk-wbt.c b/block/blk-wbt.c
index 4f89b28fa652..7beeabd05f4a 100644
--- a/block/blk-wbt.c
+++ b/block/blk-wbt.c
@@ -550,7 +550,7 @@ static inline bool may_queue(struct rq_wb *rwb, struct rq_wait *rqw,
* If the waitqueue is already active and we are not the next
* in line to be woken up, wait for our turn.
*/
- if (waitqueue_active(&rqw->wait) &&
+ if (wait && waitqueue_active(&rqw->wait) &&
rqw->wait.head.next != &wait->entry)
return false;
@@ -567,16 +567,27 @@ static void __wbt_wait(struct rq_wb *rwb, enum wbt_flags wb_acct,
__acquires(lock)
{
struct rq_wait *rqw = get_rq_wait(rwb, wb_acct);
+ struct wait_queue_entry *waitptr = NULL;
DEFINE_WAIT(wait);
- if (may_queue(rwb, rqw, &wait, rw))
+ if (may_queue(rwb, rqw, waitptr, rw))
return;
+ waitptr = &wait;
do {
- prepare_to_wait_exclusive(&rqw->wait, &wait,
+ /*
+ * Don't add ourselves to the wq tail if we've already
+ * slept. Otherwise we can penalize background writes
+ * indefinitely.
+ */
+ if (waitptr)
+ prepare_to_wait_exclusive(&rqw->wait, &wait,
+ TASK_UNINTERRUPTIBLE);
+ else
+ prepare_to_wait(&rqw->wait, &wait,
TASK_UNINTERRUPTIBLE);
- if (may_queue(rwb, rqw, &wait, rw))
+ if (may_queue(rwb, rqw, waitptr, rw))
break;
if (lock) {
@@ -585,6 +596,12 @@ static void __wbt_wait(struct rq_wb *rwb, enum wbt_flags wb_acct,
spin_lock_irq(lock);
} else
io_schedule();
+
+ /*
+ * After we've slept, we don't want to factor in wq head
+ * placement anymore for may_queue().
+ */
+ waitptr = NULL;
} while (1);
finish_wait(&rqw->wait, &wait);
--
Jens Axboe
next reply other threads:[~2018-06-22 19:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 19:26 Jens Axboe [this message]
2018-06-22 22:43 ` [PATCH] blk-wbt: fix indefinite background writeback sleep Ming Lei
2018-06-22 22:51 ` Jens Axboe
2018-06-22 23:11 ` Ming Lei
2018-06-22 23:13 ` Jens Axboe
2018-06-23 1:37 ` Ming Lei
2018-06-23 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=0fa9cc9f-7d34-2490-cdaf-fe7a761e4790@kernel.dk \
--to=axboe@kernel.dk \
--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