mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Tejun Heo <tj@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Juri Lelli <juri.lelli@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
	Valentin Schneider <vschneid@redhat.com>,
	K Prateek Nayak <kprateek.nayak@amd.com>,
	Kyle McMartin <jkkm@meta.com>
Subject: Re: [PATCH v2] sched/rt: Have RT_PUSH_IPI be default off for non PREEMPT_RT
Date: Fri, 15 May 2026 14:56:08 -0400	[thread overview]
Message-ID: <20260515145608.2039b4cf@gandalf.local.home> (raw)
In-Reply-To: <agdqVe128SUc1vCW@slm.duckdns.org>

On Fri, 15 May 2026 08:47:49 -1000
Tejun Heo <tj@kernel.org> wrote:

> Hello, Steven.
> 
> On Fri, May 15, 2026 at 02:38:47PM -0400, Steven Rostedt wrote:
> > Hmm, but I'm guessing that it still was long enough to slow down the
> > softirq to trigger it again and prevent scheduling?  
> 
> Yes, seems that way. I think the load is lower and each softirq invocation
> is relatively short (just going through the packets received in the
> meantime) but the frequency is higher.

I just want to make sure that my analysis is correct. Since only one CPU
can initiate the RT_PUSH_IPI. That for this to be a problem, other CPUs
need to be constantly running RT tasks for short periods of time so that
when the RT task schedules off the CPU, the CPU then initiates the "pull".
And it's not that it happens all at once. It's more serialized where the RT
tasks are scheduling off at different times to constantly feed the
RT_PUSH_IPI logic without seeing that it's already in place.

It would require this to happen enough times to keep the overloaded CPU
from finishing the softirq until a time when the softirq is scheduled
again. And it would maintain this abuse for long enough to trigger the
watchdog.

Does that fit the scenario of your environment?

-- Steve


  reply	other threads:[~2026-05-15 18:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15 14:37 Steven Rostedt
2026-05-15 17:17 ` Tejun Heo
2026-05-15 18:38   ` Steven Rostedt
2026-05-15 18:47     ` Tejun Heo
2026-05-15 18:56       ` Steven Rostedt [this message]
2026-05-15 22:27         ` Tejun Heo
2026-05-18  8:47 ` Valentin Schneider
2026-05-20  6:33   ` Shrikanth Hegde
2026-05-20 16:52     ` Steven Rostedt
2026-05-20 17:04       ` Shrikanth Hegde
2026-05-20 18:09         ` Tejun Heo
2026-05-20 19:02           ` Steven Rostedt
2026-05-20 19:37             ` Tejun Heo
2026-05-21 10:11     ` Valentin Schneider
2026-05-20  8:33 ` [tip: sched/core] " tip-bot2 for 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=20260515145608.2039b4cf@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=jkkm@meta.com \
    --cc=juri.lelli@redhat.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=peterz@infradead.org \
    --cc=tj@kernel.org \
    --cc=vincent.guittot@linaro.org \
    --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®