From: Xiongfeng Wang <wangxiongfeng2@huawei.com>
To: <axboe@kernel.dk>, <hch@lst.de>
Cc: <linux-block@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<yuyufen@huawei.com>, <guohanjun@huawei.com>,
<wangxiongfeng2@huawei.com>
Subject: [RFC PATCH] blk-mq: avoid housekeeping CPUs scheduling a worker on a non-housekeeping CPU
Date: Thu, 10 Feb 2022 17:35:32 +0800 [thread overview]
Message-ID: <20220210093532.182818-1-wangxiongfeng2@huawei.com> (raw)
When NOHZ_FULL is enabled, such as in HPC situation, CPUs are divided
into housekeeping CPUs and non-housekeeping CPUs. Non-housekeeping CPUs
are NOHZ_FULL CPUs and are often monopolized by the userspace process,
such HPC application process. Any sort of interruption is not expected.
blk_mq_hctx_next_cpu() selects each cpu in 'hctx->cpumask' alternately
to schedule the work thread blk_mq_run_work_fn(). When 'hctx->cpumask'
contains housekeeping CPU and non-housekeeping CPU at the same time, a
housekeeping CPU, which want to request a IO, may schedule a worker on a
non-housekeeping CPU. This may affect the performance of the userspace
application running on non-housekeeping CPUs.
So let's just schedule the worker thread on the current CPU when the
current CPU is housekeeping CPU.
Signed-off-by: Xiongfeng Wang <wangxiongfeng2@huawei.com>
---
block/blk-mq.c | 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/block/blk-mq.c b/block/blk-mq.c
index 1adfe4824ef5..ff9a4bf16858 100644
--- a/block/blk-mq.c
+++ b/block/blk-mq.c
@@ -24,6 +24,7 @@
#include <linux/sched/sysctl.h>
#include <linux/sched/topology.h>
#include <linux/sched/signal.h>
+#include <linux/sched/isolation.h>
#include <linux/delay.h>
#include <linux/crash_dump.h>
#include <linux/prefetch.h>
@@ -2036,6 +2037,8 @@ static int blk_mq_hctx_next_cpu(struct blk_mq_hw_ctx *hctx)
static void __blk_mq_delay_run_hw_queue(struct blk_mq_hw_ctx *hctx, bool async,
unsigned long msecs)
{
+ int work_cpu;
+
if (unlikely(blk_mq_hctx_stopped(hctx)))
return;
@@ -2050,7 +2053,17 @@ static void __blk_mq_delay_run_hw_queue(struct blk_mq_hw_ctx *hctx, bool async,
put_cpu();
}
- kblockd_mod_delayed_work_on(blk_mq_hctx_next_cpu(hctx), &hctx->run_work,
+ /*
+ * Avoid housekeeping CPUs scheduling a worker on a non-housekeeping
+ * CPU
+ */
+ if (tick_nohz_full_enabled() && housekeeping_cpu(smp_processor_id(),
+ HK_FLAG_WQ))
+ work_cpu = smp_processor_id();
+ else
+ work_cpu = blk_mq_hctx_next_cpu(hctx);
+
+ kblockd_mod_delayed_work_on(work_cpu, &hctx->run_work,
msecs_to_jiffies(msecs));
}
--
2.20.1
next reply other threads:[~2022-02-10 9:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 9:35 Xiongfeng Wang [this message]
2022-02-15 2:29 ` [RFC PATCH] blk-mq: avoid housekeeping CPUs scheduling a worker on a non-housekeeping CPU Xiongfeng Wang
2022-02-15 4:37 ` Ming Lei
2022-02-15 9:32 ` Xiongfeng Wang
2022-02-15 9:38 ` Xiongfeng Wang
-- strict thread matches above, loose matches on Subject: below --
2023-02-23 7:48 Xiongfeng Wang
2023-02-23 15:06 ` Christoph Hellwig
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=20220210093532.182818-1-wangxiongfeng2@huawei.com \
--to=wangxiongfeng2@huawei.com \
--cc=axboe@kernel.dk \
--cc=guohanjun@huawei.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yuyufen@huawei.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