From: Guopeng Zhang <guopeng.zhang@linux.dev>
To: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
K Prateek Nayak <kprateek.nayak@amd.com>,
linux-kernel@vger.kernel.org,
Guopeng Zhang <zhangguopeng@kylinos.cn>,
Christian Loehle <christian.loehle@arm.com>
Subject: Re: [PATCH] sched/deadline: Exclude special DL entities from bandwidth moves
Date: Mon, 29 Jun 2026 13:43:34 +0800 [thread overview]
Message-ID: <d19f6ccc-998f-4692-93e8-463c67537218@linux.dev> (raw)
In-Reply-To: <ahg0F_zVXq3CRHGe@jlelli-thinkpadt14gen4.remote.csb>
Hi Peter, Ingo,
Gentle ping on this patch.
It has received Reviewed-by from Christian and Acked-by from Juri.
Do you think it is suitable for the sched/core tree, or is there anything
else I should change?
Thanks,
Guopeng
在 2026/5/28 20:24, Juri Lelli 写道:
> Hello!
>
> On 28/05/26 14:53, Guopeng Zhang wrote:
>> From: Guopeng Zhang <zhangguopeng@kylinos.cn>
>>
>> SUGOV special DL entities use fake/unused bandwidth. They are already
>> excluded from regular DL admission control, affinity admission checks,
>> rq bandwidth accounting, and root-domain rebuild accounting.
>>
>> dl_task_needs_bw_move() misses the same exclusion. As a result,
>> set_cpus_allowed_dl() and cpuset attach may treat a special DL entity as
>> requiring a root-domain bandwidth move when its affinity mask no longer
>> intersects the source root domain.
>>
>> Return false for special DL entities so root-domain bandwidth move
>> accounting follows the rest of the SUGOV special-entity handling.
>>
>> Signed-off-by: Guopeng Zhang <zhangguopeng@kylinos.cn>
>> ---
>> kernel/sched/deadline.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
>> index ddfd6bc63ab1..3653166caa69 100644
>> --- a/kernel/sched/deadline.c
>> +++ b/kernel/sched/deadline.c
>> @@ -3142,7 +3142,7 @@ static void set_cpus_allowed_dl(struct task_struct *p,
>> bool dl_task_needs_bw_move(struct task_struct *p,
>> const struct cpumask *new_mask)
>> {
>> - if (!dl_task(p))
>> + if (!dl_task(p) || dl_entity_is_special(&p->dl))
>> return false;
>>
>> return !cpumask_intersects(task_rq(p)->rd->span, new_mask);
>
> Makes sense to me.
>
> Acked-by: Juri Lelli <juri.lelli@redhat.com>
>
> Best,
> Juri
>
prev parent reply other threads:[~2026-06-29 5:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 6:53 [PATCH] sched/deadline: Exclude special DL entities from bandwidth moves Guopeng Zhang
2026-05-28 9:47 ` Christian Loehle
2026-05-28 12:24 ` Juri Lelli
2026-06-29 5:43 ` Guopeng Zhang [this message]
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=d19f6ccc-998f-4692-93e8-463c67537218@linux.dev \
--to=guopeng.zhang@linux.dev \
--cc=bsegall@google.com \
--cc=christian.loehle@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=zhangguopeng@kylinos.cn \
/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