From: Peter Zijlstra <peterz@infradead.org>
To: Mel Gorman <mgorman@techsingularity.net>
Cc: Ingo Molnar <mingo@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Steven Rostedt <rostedt@goodmis.org>,
Seiji Nishikawa <snishika@redhat.com>,
Mian Yousaf Kaukab <ykaukab@suse.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] sched/rt: Do not account migrate-disabled tasks as pushable
Date: Tue, 17 Nov 2026 16:10:51 +0100 [thread overview]
Message-ID: <20261117151051.GH1813469@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <avxht-AL1t6I6IXA@techsingularity.net>
On Tue, Nov 17, 2026 at 02:27:38PM +0000, Mel Gorman wrote:
> On Fri, Nov 13, 2026 at 04:06:55PM +0000, Mel Gorman wrote:
> > RT_PUSH_IPI is intended to minimise latency and rq lock contention when
> > migrating tasks to balance RT task distribution. The problem is that
> > if a CPU is rt_overloaded but has no tasks that can be pushed then IPIs
> > can be fired continually at the same CPU but fail to move any task due
> > to migrate_disable() on PREEMPT_RT. A specific case was "pgrep" running
> > at RT priority, its CPU being the target of a continuous stream of IPIs
> > without any task moving. While the pgrep can be bound to another CPU by
> > the application, the underlying problem was that pgrep is spinlock-intensive
> > which disables migration on PREEMPT_RT.
> >
>
> I know the rate of scheduler patches at the moment is completely insane
> but is there anything else I should do with this patch?
IKR :/ Let me go have a look.
next prev parent reply other threads:[~2026-11-17 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 16:06 Mel Gorman
2026-11-17 14:27 ` Mel Gorman
2026-11-17 15:10 ` Peter Zijlstra [this message]
2026-11-17 15:20 ` Peter Zijlstra
2026-11-17 15:24 ` Peter Zijlstra
2026-11-17 15:25 ` Steven Rostedt
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=20261117151051.GH1813469@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=snishika@redhat.com \
--cc=vincent.guittot@linaro.org \
--cc=ykaukab@suse.de \
/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®