[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230613092819.GA18487@didi-ThinkCentre-M930t-N000>
Date: Tue, 13 Jun 2023 17:28:19 +0800
From: tiozhang <tiozhang@...iglobal.com>
To: <mingo@...hat.com>, <peterz@...radead.org>,
<juri.lelli@...hat.com>, <vincent.guittot@...aro.org>,
<tj@...nel.org>
CC: <dietmar.eggemann@....com>, <rostedt@...dmis.org>,
<bsegall@...gle.com>, <mgorman@...e.de>, <bristot@...hat.com>,
<vschneid@...hat.com>, <zyhtheonly@...il.com>,
<tiozhang@...iglobal.com>, <zwp10758@...il.com>,
<fuyuanli@...iglobal.com>, <zyhtheonly@...h.net>,
<linux-kernel@...r.kernel.org>
Subject: [PATCH] sched/isolation: add a workqueue parameter to constrain
unbound CPUs
Motivation of doing this is to better improve boot times for devices when
we want to prevent our workqueue works from running on some specific CPUs,
i,e, some CPUs are busy with interrupts.
Suggested-by: Tejun Heo <tj@...nel.org>
Signed-off-by: tiozhang <tiozhang@...iglobal.com>
---
kernel/sched/isolation.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/kernel/sched/isolation.c b/kernel/sched/isolation.c
index 373d42c707bc..85e744c1349a 100644
--- a/kernel/sched/isolation.c
+++ b/kernel/sched/isolation.c
@@ -208,6 +208,12 @@ static int __init housekeeping_isolcpus_setup(char *str)
continue;
}
+ if (!strncmp(str, "workqueue,", 10)) {
+ str += 10;
+ flags |= HK_FLAG_WQ;
+ continue;
+ }
+
if (!strncmp(str, "managed_irq,", 12)) {
str += 12;
flags |= HK_FLAG_MANAGED_IRQ;
--
2.17.1
Powered by blists - more mailing lists