From: Francesco Nigro <nigro.fra@gmail.com>
To: Mike Galbraith <efault@gmx.de>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Valentin Schneider <vschneid@redhat.com>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Huang Rui <ray.huang@amd.com>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [REPORT] sched: ITMT + DELAY_DEQUEUE: woken task waits ~1 ms behind another task on the preferred CPU while allowed CPUs are idle
Date: Wed, 4 Nov 2026 00:33:52 +0100 [thread overview]
Message-ID: <20261103233352.2282883-1-nigro.fra@gmail.com> (raw)
In-Reply-To: <25edb6cd36cb77b82b40826b97232438f1443516.camel@gmx.de>
On Tue, 2026-11-03 at 18:27 +0100, Mike Galbraith wrote:
> Mmm, that's a be careful what you wish for thing.
[...]
> Not a keeper.
Thanks, that answers my second question for your patch; I had listed
it as earlier work on the same step.
The stalls in the report happen when both busy threads are on CPU 6
at the same time. What the report doesn't show is where the two threads
run the rest of the time. With ITMT on, both run almost only on CPUs 6
and 7, the two highest-ranked of the four: each starts about half of
its bursts on each, and under 3 % on CPUs 4 and 5. With ITMT off, the
two threads' main CPUs differ in every run (run 1: one thread starts
99.9 % of its bursts on CPU 5, the other 100 % on CPU 6). Per-CPU burst
counts from the earlier reproducer (asym_stack2.c), 5 runs of 30 s:
https://github.com/franz1981/itmt-delay-dequeue-repro/blob/49b6d72cb41d2535964c87a660178dd636d1d366/results-final.txt
Is it expected that ITMT keeps two busy threads on the same two
top-ranked CPUs, sometimes on the same one, while the other allowed
CPUs are idle?
Thanks,
Franz
next prev parent reply other threads:[~2026-11-03 23:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 15:46 Francesco Nigro
2026-11-03 17:27 ` Mike Galbraith
2026-11-03 23:33 ` Francesco Nigro [this message]
2026-11-04 3:13 ` Mike Galbraith
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=20261103233352.2282883-1-nigro.fra@gmail.com \
--to=nigro.fra@gmail.com \
--cc=dietmar.eggemann@arm.com \
--cc=efault@gmx.de \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=ray.huang@amd.com \
--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®