public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: "Doug Smythies" <dsmythies@telus.net>
To: "'Harshvardhan Jha'" <harshvardhan.j.jha@oracle.com>
Cc: "'Sasha Levin'" <sashal@kernel.org>,
	"'Greg Kroah-Hartman'" <gregkh@linuxfoundation.org>,
	<linux-pm@vger.kernel.org>, <stable@vger.kernel.org>,
	"Doug Smythies" <dsmythies@telus.net>,
	"'Christian Loehle'" <christian.loehle@arm.com>,
	"'Rafael J. Wysocki'" <rafael@kernel.org>,
	"'Daniel Lezcano'" <daniel.lezcano@linaro.org>
Subject: RE: Performance regressions introduced via Revert "cpuidle: menu: Avoid discarding useful information" on 5.15 LTS
Date: Wed, 3 Dec 2025 14:30:42 -0800	[thread overview]
Message-ID: <005401dc64a4$75f1d770$61d58650$@telus.net> (raw)
In-Reply-To: <39c7d882-6711-4178-bce6-c1e4fc909b84@arm.com>

[-- Attachment #1: Type: text/plain, Size: 3917 bytes --]

On 2025.12.03 08:45 Christian Loehle wrote:
> On 12/3/25 16:18, Harshvardhan Jha wrote:
>> Hi there,
>> 
>> While running performance benchmarks for the 5.15.196 LTS tags , it was
>> observed that several regressions across different benchmarks is being
>> introduced when compared to the previous 5.15.193 kernel tag. Running an
>> automated bisect on both of them narrowed down the culprit commit to:
>> - 5666bcc3c00f7 Revert "cpuidle: menu: Avoid discarding useful
>> information" for 5.15
>> 
>> Regressions on 5.15.196 include:
>> -9.3% : Phoronix pts/sqlite using 2 processes on OnPrem X6-2
>> -6.3% : Phoronix system/sqlite on OnPrem X6-2
>> -18%  : rds-stress -M 1 (readonly rdma-mode) metrics with 1 depth & 1
>> thread & 1M buffer size on OnPrem X6-2
>> -4 -> -8% : rds-stress -M 2 (writeonly rdma-mode) metrics with 1 depth &
>> 1 thread & 1M buffer size on OnPrem X6-2
>> Up to -30% : Some Netpipe metrics on OnPrem X5-2
>> 
>> The culprit commits' messages mention that these reverts were done due
>> to performance regressions introduced in Intel Jasper Lake systems but
>> this revert is causing issues in other systems unfortunately. I wanted
>> to know the maintainers' opinion on how we should proceed in order to
>> fix this. If we reapply it'll bring back the previous regressions on
>> Jasper Lake systems and if we don't revert it then it's stuck with
>> current regressions. If this problem has been reported before and a fix
>> is in the works then please let me know I shall follow developments to
>> that mail thread.
>
> The discussion regarding this can be found here:
> https://lore.kernel.org/lkml/36iykr223vmcfsoysexug6s274nq2oimcu55ybn6ww4il3g3cv@cohflgdbpnq7/
> we explored an alternative to the full revert here:
> https://lore.kernel.org/lkml/4687373.LvFx2qVVIh@rafael.j.wysocki/
> unfortunately that didn't lead anywhere useful, so Rafael went with the
> full revert you're seeing now.
>
> Ultimately it seems to me that this "aggressiveness" on deep idle tradeoffs
> will highly depend on your platform, but also your workload, Jasper Lake
> in particular seems to favor deep idle states even when they don't seem
> to be a 'good' choice from a purely cpuidle (governor) perspective, so
> we're kind of stuck with that.
>
> For teo we've discussed a tunable knob in the past, which comes naturally with
> the logic, for menu there's nothing obvious that would be comparable.
> But for teo such a knob didn't generate any further interest (so far).
>
> That's the status, unless I missed anything?

By reading everything in the links Chrsitian provided, you can see
that we had difficulties repeating test results on other platforms.

Of the tests listed herein, the only one that was easy to repeat on my
test server, was the " Phoronix pts/sqlite" one. I got (summary: no difference):

Kernel 6.18									Reverted			
pts/sqlite-2.3.0			menu rc4		menu rc1		menu rc1		menu rc3	
				performance		performance		performance		performance	
test	what			ave			ave			ave			ave	
1	T/C 1			2.147	-0.2%		2.143	0.0%		2.16	-0.8%		2.156	-0.6%
2	T/C 2			3.468	0.1%		3.473	0.0%		3.486	-0.4%		3.478	-0.1%
3	T/C 4			4.336	0.3%		4.35	0.0%		4.355	-0.1%		4.354	-0.1%
4	T/C 8			5.438	-0.1%		5.434	0.0%		5.456	-0.4%		5.45	-0.3%
5	T/C 12			6.314	-0.2%		6.299	0.0%		6.307	-0.1%		6.29	0.1%

Where:
T/C means: Threads / Copies
performance means: intel_pstate CPU frequency scaling driver and the performance CPU frequencay scaling governor.
Data points are in Seconds.
Ave means the average test result. The number of runs per test was increased from the default of 3 to 10.
The reversion was manually applied to kernel 6.18-rc1 for that test.
The reversion was included in kernel 6.18-rc3.
Kernel 6.18-rc4 had another code change to menu.c

In case the formatting gets messed up, the table is also attached.

Processor: Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz, 6 cores 12 CPUs.
HWP: Enabled.
 
... Doug


[-- Attachment #2: sqlite-test-table.png --]
[-- Type: image/png, Size: 21984 bytes --]

  reply	other threads:[~2025-12-03 22:30 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-03 16:18 Performance regressions introduced via Revert "cpuidle: menu: Avoid discarding useful information" on 5.15 LTS Harshvardhan Jha
2025-12-03 16:44 ` Christian Loehle
2025-12-03 22:30   ` Doug Smythies [this message]
2025-12-08 11:33     ` Harshvardhan Jha
2025-12-08 12:47       ` Christian Loehle
2026-01-13  7:06         ` Harshvardhan Jha
2026-01-13 14:13           ` Rafael J. Wysocki
2026-01-13 14:18             ` Rafael J. Wysocki
2026-01-14  4:28               ` Sergey Senozhatsky
2026-01-14  4:49                 ` Sergey Senozhatsky
2026-01-14  5:15                   ` Tomasz Figa
2026-01-14 20:07                     ` Rafael J. Wysocki
2026-01-29 10:23                       ` Harshvardhan Jha
2026-01-29 22:47                   ` Doug Smythies
2026-01-27 15:45         ` Harshvardhan Jha
2026-01-28  5:06           ` Doug Smythies
2026-01-28 23:53             ` Doug Smythies
2026-01-29 22:27               ` Doug Smythies
2026-01-30 19:28                 ` Rafael J. Wysocki
2026-02-01 19:20                   ` Christian Loehle
2026-02-02 17:31                     ` Harshvardhan Jha
2026-02-03  9:07                       ` Christian Loehle
2026-02-03  9:16                         ` Harshvardhan Jha
2026-02-03  9:31                           ` Christian Loehle
2026-02-03 10:22                             ` Harshvardhan Jha
2026-02-03 10:30                               ` Christian Loehle
2026-02-03 16:45                             ` Rafael J. Wysocki
2026-02-05  0:45                               ` Doug Smythies
2026-02-05  2:37                                 ` Sergey Senozhatsky
2026-02-05  5:18                                   ` Doug Smythies
2026-02-10  9:17                                     ` Sergey Senozhatsky
2026-02-11  4:27                                       ` Doug Smythies
2026-02-05  7:15                                   ` Christian Loehle
2026-02-10  8:02                                     ` Sergey Senozhatsky
2026-02-10  8:57                                       ` Christian Loehle
2026-02-11  4:27                                         ` Doug Smythies
2026-02-05  5:02                                 ` Doug Smythies
2026-02-10  9:33                                   ` Xueqin Luo
2026-02-10 10:04                                     ` Sergey Senozhatsky
2026-02-10 14:24                                       ` Rafael J. Wysocki
2026-02-11  1:34                                         ` Sergey Senozhatsky
2026-02-11  4:17                                           ` Doug Smythies
2026-02-11  8:58                                         ` Xueqin Luo
2026-02-10 14:20                                     ` Rafael J. Wysocki

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='005401dc64a4$75f1d770$61d58650$@telus.net' \
    --to=dsmythies@telus.net \
    --cc=christian.loehle@arm.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=harshvardhan.j.jha@oracle.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    /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