From: Abel Wu <wuyun.abel@bytedance.com>
To: Madadi Vineeth Reddy <vineethr@linux.ibm.com>
Cc: "open list:SCHEDULER" <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
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>,
Josh Don <joshdon@google.com>,
Valentin Schneider <vschneid@redhat.com>,
Tianchen Ding <dtcccc@linux.alibaba.com>
Subject: Re: Re: [PATCH 1/2] sched/fair: Do not let idle entities preempt others
Date: Sun, 23 Feb 2025 16:45:54 +0800 [thread overview]
Message-ID: <e7a81f13-6f09-4a7a-9d85-0ba4885442bc@bytedance.com> (raw)
In-Reply-To: <e7c4d27f-6b98-4cd6-85b8-9c4672acdef4@linux.ibm.com>
On 2/23/25 1:48 AM, Madadi Vineeth Reddy Wrote:
> On 21/02/25 16:42, Abel Wu wrote:
>> A task with SCHED_IDLE policy doesn't preempt others by definition, and
>> the semantics are intended to be preserved when extending to cgroups
>> introduced in commit 304000390f88 ("sched: Cgroup SCHED_IDLE support").
>
> [snip]
>
>> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
>> index 1c0ef435a7aa..4340178f29b7 100644
>> --- a/kernel/sched/fair.c
>> +++ b/kernel/sched/fair.c
>> @@ -8778,12 +8778,15 @@ static void check_preempt_wakeup_fair(struct rq *rq, struct task_struct *p, int
>> pse_is_idle = se_is_idle(pse);
>>
>> /*
>> - * Preempt an idle entity in favor of a non-idle entity (and don't preempt
>> - * in the inverse case).
>> + * Preempt an idle entity in favor of a non-idle entity.
>> */
>> if (cse_is_idle && !pse_is_idle)
>> goto preempt;
>
> This patch doesn't apply cleanly on top of tip/sched/core because of the
> commit f553741ac8c0 ("sched: Cancel the slice protection of the idle entity").
> Please rebase it.
Will rebase. Thanks!
>
> Thanks,
> Madadi Vineeth Reddy
>
>> - if (cse_is_idle != pse_is_idle)
>> +
>> + /*
>> + * IDLE entities do not preempt others.
>> + */
>> + if (unlikely(pse_is_idle))
>> return;
>>
>> /*
>
next prev parent reply other threads:[~2025-02-23 8:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 11:12 [PATCH 0/2] Fix SCHED_IDLE behavior on wakeup preemption Abel Wu
2025-02-21 11:12 ` [PATCH 1/2] sched/fair: Do not let idle entities preempt others Abel Wu
2025-02-21 11:48 ` Vincent Guittot
2025-02-21 19:54 ` Josh Don
2025-02-22 17:12 ` Madadi Vineeth Reddy
2025-02-22 17:48 ` Madadi Vineeth Reddy
2025-02-23 8:45 ` Abel Wu [this message]
2025-02-21 11:12 ` [PATCH 2/2] sched/fair: Fix premature check of WAKEUP_PREEMPTION Abel Wu
2025-02-21 11:49 ` Vincent Guittot
2025-02-21 15:57 ` Abel Wu
2025-02-22 18:16 ` Madadi Vineeth Reddy
2025-02-23 8:44 ` Abel Wu
2025-02-23 10:25 ` Madadi Vineeth Reddy
2025-02-23 11:22 ` Abel Wu
2025-02-24 13:47 ` Vincent Guittot
2025-02-24 14:10 ` Phil Auld
2025-02-25 17:14 ` Vincent Guittot
2025-02-25 6:29 ` Abel Wu
2025-02-25 17:15 ` Vincent Guittot
2025-02-26 7:34 ` Abel Wu
2025-02-25 6:56 ` Tianchen Ding
2025-02-24 13:22 ` Vincent Guittot
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=e7a81f13-6f09-4a7a-9d85-0ba4885442bc@bytedance.com \
--to=wuyun.abel@bytedance.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=dtcccc@linux.alibaba.com \
--cc=joshdon@google.com \
--cc=juri.lelli@redhat.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=vineethr@linux.ibm.com \
--cc=vschneid@redhat.com \
/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
all inboxes | Powered by JetHome®