[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aJ3bwJ5eRtjffd-u@jlelli-thinkpadt14gen4.remote.csb>
Date: Thu, 14 Aug 2025 14:51:12 +0200
From: Juri Lelli <juri.lelli@...hat.com>
To: Yuri Andriaccio <yurand2000@...il.com>
Cc: Ingo Molnar <mingo@...hat.com>, Peter Zijlstra <peterz@...radead.org>,
Vincent Guittot <vincent.guittot@...aro.org>,
Dietmar Eggemann <dietmar.eggemann@....com>,
Steven Rostedt <rostedt@...dmis.org>,
Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>,
Valentin Schneider <vschneid@...hat.com>,
linux-kernel@...r.kernel.org,
Luca Abeni <luca.abeni@...tannapisa.it>,
Yuri Andriaccio <yuri.andriaccio@...tannapisa.it>
Subject: Re: [RFC PATCH v2 07/25] sched/rt: Introduce HCBS specific structs
in task_group
Hi!
On 31/07/25 12:55, Yuri Andriaccio wrote:
...
> @@ -467,9 +474,15 @@ struct task_group {
>
> #ifdef CONFIG_RT_GROUP_SCHED
> struct sched_rt_entity **rt_se;
> + /*
> + * The scheduling entities for the task group are managed as a single
> + * sched_dl_entity, each of them sharing the same dl_bandwidth.
> + */
> + struct sched_dl_entity **dl_se;
This is actually one sched_dl_entity per CPU, right? If that is the case
the comment is a little misleading I am afraid (mentioning single
entitiy).
Thanks,
Juri
Powered by blists - more mailing lists