mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Abel Wu <wuyun.abel@bytedance.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: Madadi Vineeth Reddy <vineethr@linux.ibm.com>,
	Phil Auld <pauld@redhat.com>, Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Juri Lelli <juri.lelli@redhat.com>,
	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>,
	Josh Don <joshdon@google.com>,
	Tianchen Ding <dtcccc@linux.alibaba.com>,
	"open list:SCHEDULER" <linux-kernel@vger.kernel.org>
Subject: Re: Re: [PATCH v2 2/2] sched/fair: Fix premature check of WAKEUP_PREEMPTION
Date: Mon, 3 Mar 2025 11:32:23 +0800	[thread overview]
Message-ID: <3cc57824-4a99-4bdc-9283-ca73bdc2fa50@bytedance.com> (raw)
In-Reply-To: <CAKfTPtBj2xhVg1BA5q6cC57TFGVBtgz6bbKrWGkjStSUKdxpgg@mail.gmail.com>

On 2/28/25 10:26 PM, Vincent Guittot wrote:
> On Thu, 27 Feb 2025 at 09:58, Abel Wu <wuyun.abel@bytedance.com> wrote:
>>
>> The commit 6bc912b71b6f ("sched: SCHED_OTHER vs SCHED_IDLE isolation")
>> defines the behavior of SCHED_IDLE as following:
>>
>>   - no SCHED_IDLE buddies
>>   - never let SCHED_IDLE preempt on wakeup
>>   - always preempt SCHED_IDLE on wakeup
>>   - limit SLEEPER fairness for SCHED_IDLE
>>
>> and the 3rd rule is broken if !WAKEUP_PREEMPTION due to recently merged
>> commit faa42d29419d ("sched/fair: Make SCHED_IDLE entity be preempted in strict hierarchy")
>>
>> Although WAKEUP_PREEMPTION is mainly there for debug purpose to provide
>> a way to check whether a performance degrade of certain workload is due
>> to overscheduling or not, it is still kind of weird that we treat sched-
>> idle cpus as idle but don't let the non-idle tasks preempt the sched-idle
>> cpus in debug mode (!WAKEUP_PREEMPTION).
>>
>> Fix it by strictly following the aforementioned rules.
>>
>> Fixes: faa42d29419d ("sched/fair: Make SCHED_IDLE entity be preempted in strict hierarchy")
>> Signed-off-by: Abel Wu <wuyun.abel@bytedance.com>
> 
> WAKEUP_PREEMPTION seems to be still used so
> 
> Acked-by: Vincent Guittot <vincent.guittot@linaro.org>

Thanks!


  reply	other threads:[~2025-03-03  3:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27  8:58 [PATCH v2 0/2] Fix SCHED_IDLE behavior on wakeup preemption Abel Wu
2025-02-27  8:58 ` [PATCH v2 1/2] sched/fair: Do not let idle entities preempt others Abel Wu
2025-02-27  8:58 ` [PATCH v2 2/2] sched/fair: Fix premature check of WAKEUP_PREEMPTION Abel Wu
2025-02-28 14:26   ` Vincent Guittot
2025-03-03  3:32     ` Abel Wu [this message]
2025-02-28  8:05 ` [PATCH v2 0/2] Fix SCHED_IDLE behavior on wakeup preemption K Prateek Nayak
2025-03-03  3:30   ` Abel Wu

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=3cc57824-4a99-4bdc-9283-ca73bdc2fa50@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=pauld@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®