[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1823b6fd-037f-38dc-2d33-0879d77768c3@bytedance.com>
Date: Wed, 6 Sep 2023 14:45:39 +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
Subject: Re: [PATCH 0/2] Fix nohz_full vs rt bandwidth
Friendly ping...
On 2023/8/21 Hao Jia wrote:
> 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(-)
>
Powered by blists - more mailing lists