mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 23:06:22 +0100	[thread overview]
Message-ID: <20261104220622.3542344-1-nigro.fra@gmail.com> (raw)
In-Reply-To: <32db09358aecb92c55c8c1295fa71b6a73306999.camel@gmx.de>

On Wed, 2026-11-04 at 04:13 +0100, Mike Galbraith wrote:
> In your specific case, dunno.  In general, absolutely.

I checked with boost on too, on the same box and kernel. I ran
asym_min and tbench on CPUs 4-7, without SMT siblings, with clocks
pinned and boost off, and with boost on and the full frequency
range, DELAY_DEQUEUE on.

With boost on, 0.82-1.09 % of asym_min wakeups per run waited at
least 0.5 ms with ITMT on, and none with ITMT off.

tbench throughput was the same with ITMT on or off in every setting
(within 1 %), and so was the busy CPUs' clock (within 0.2 %).
According to these new runs, with boost on ITMT gives no throughput
advantage and still causes the long stalls.

As a side note, I agree about DELAY_DEQUEUE: disabling it reduced
tbench throughput at full load, with ITMT on or off.

Scripts and raw output:
https://github.com/franz1981/itmt-delay-dequeue-repro/tree/1400f15

Tool use as in the report.

Thanks,
Franz

      reply	other threads:[~2026-11-04 22:06 UTC|newest]

Thread overview: 5+ 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
2026-11-04  3:13     ` Mike Galbraith
2026-11-04 22:06       ` Francesco Nigro [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=20261104220622.3542344-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®