[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230821094927.51079-1-jiahao.os@bytedance.com>
Date: Mon, 21 Aug 2023 17:49:25 +0800
From: Hao Jia <jiahao.os@...edance.com>
To: mingo@...hat.com, peterz@...radead.org, mingo@...nel.org,
juri.lelli@...hat.com, vincent.guittot@...aro.org,
dietmar.eggemann@....com, rostedt@...dmis.org, bsegall@...gle.com,
mgorman@...e.de, bristot@...hat.com, vschneid@...hat.com,
pauld@...hat.com
Cc: linux-kernel@...r.kernel.org, Hao Jia <jiahao.os@...edance.com>
Subject: [PATCH 0/2] Fix nohz_full vs rt bandwidth
Since the commit 88c56cfeaec4 ("sched/fair: Block nohz tick_stop
when cfs bandwidth in use") was merged, it handles conflicts between
NOHZ full and cfs_bandwidth well, and the scheduler feature HZ_BW
allows us to choose which one to prefer.
This conflict also exists between NOHZ full and rt_bandwidth,
these two patches try to handle it in a similar way.
patch1: Extracts a can_stop_tick() callback function for each
sched_class from sched_can_stop_tick(), it will make things clearer
and also convenient to handle the conflict between NOHZ full
and rt_bandwidth.
patch2: If the HZ_BW scheduler feature is enabled, and the RT task
to be run is constrained by rt_bandwidth runtime. Then it will
prevent NO_HZ full from stopping tick.
Hao Jia (2):
sched/core: Introduce sched_class::can_stop_tick()
sched/rt: Block nohz tick_stop when rt bandwidth in use
kernel/sched/core.c | 67 +++++--------------------------
kernel/sched/deadline.c | 16 ++++++++
kernel/sched/fair.c | 56 +++++++++++++++++++++++---
kernel/sched/rt.c | 89 ++++++++++++++++++++++++++++++++++++++++-
kernel/sched/sched.h | 5 ++-
5 files changed, 168 insertions(+), 65 deletions(-)
--
2.39.2
Powered by blists - more mailing lists