From: Abel Wu <wuyun.abel@bytedance.com>
To: K Prateek Nayak <kprateek.nayak@amd.com>,
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>,
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>,
Josh Don <joshdon@google.com>,
Tianchen Ding <dtcccc@linux.alibaba.com>
Cc: "open list:SCHEDULER" <linux-kernel@vger.kernel.org>
Subject: Re: Re: [PATCH v2 0/2] Fix SCHED_IDLE behavior on wakeup preemption
Date: Mon, 3 Mar 2025 11:30:07 +0800 [thread overview]
Message-ID: <033b4ec3-cbbd-4aa8-b25b-3bb4bdbaced9@bytedance.com> (raw)
In-Reply-To: <3ce5065e-8b9b-46a8-b7c1-5f9b8f118b06@amd.com>
On 2/28/25 4:05 PM, K Prateek Nayak wrote:
> Hello Abel,
>
> On 2/27/2025 2:28 PM, Abel Wu 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 middle two of them are broken now.
>
> Feel free to include:
>
> Tested-by: K Prateek Nayak <kprateek.nayak@amd.com>
Thanks!
prev parent reply other threads:[~2025-03-03 3:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 8:58 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
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 [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=033b4ec3-cbbd-4aa8-b25b-3bb4bdbaced9@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=kprateek.nayak@amd.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®