From: David Laight <David.Laight@ACULAB.COM>
To: Linux kernel regressions list <regressions@lists.linux.dev>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: RE: Linux 6.10-rc2 - massive performance regression
Date: Sun, 9 Jun 2024 09:35:36 +0000 [thread overview]
Message-ID: <930d66db93814520be94f02ee62a19e6@AcuMS.aculab.com> (raw)
In-Reply-To: <ebf5c056-3035-4e76-9472-d76be6427669@leemhuis.info>
From: Linux regression tracking (Thorsten Leemhuis)
> Sent: 09 June 2024 09:11
>
> On 09.06.24 00:00, Linus Torvalds wrote:
> > On Sat, 8 Jun 2024 at 14:36, David Laight <David.Laight@aculab.com> wrote:
> > [...]
> >> I've done some tests.
> >> I'm seeing a three-fold slow down on:
> >> $ i=0; while [ $i -lt 1000000 ]; do i=$((i + 1)); done
> >> which goes from 1 second to 3.
> >>
> >> I can run that with ftrace monitoring scheduler events (and a few
> >> other things) and can't spot anywhere the process isn't running
> >> for a significant time.
> >
> > Sounds like cpu frequency. Almost certainly hw-specific. I went
> > through that on my Threadripper in the 6.9 timeframe, but I'm not
> > seeing any issues in this current release.
>
> David, what kind of hardware do you use?
This is on an 17-7700 (4 cores + hyperthreading enabled = 8 cpu).
> Johan Hovold as
> man-in-the-middle just reported "CPU frequency of the big cores on the
> Lenovo ThinkPad X13s sometimes appears to get stuck at a low frequency
> with 6.10-rc2" and confirmed "that once the cores are fully throttled
> (using the stepwise thermal governor) due to the skin temperature
> reaching the
> first trip point, scaling_max_freq gets stuck at the next OPP".
That's not what I'm seeing.
I can turn the speed up and down by stopping/starting a daemon we use
for processing audio.
(I can give anyone a copy; it is freely downloadable from the company
web site - if you know exactly where to look!)
Basically that ends up running a bit of code on every cpu every 10ms.
There is a big difference in the number of sched_migrate_task traces
between 6.9 and 6.10 (15 v 83).
I suspect that the underlying problem is that the cpu governor
doesn't allow for a 'busy' process being moved to an idle cpu?
So if you bounce a process about it always runs an 800MHz.
My dmesg (6.9 and 6.10) has:
cpuidle: using governor idle
cpuidle: using governor ladder
But I had a feeling that some 'hardware magic' changes the cpu
speed on these systems?
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2024-06-09 9:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-02 22:50 Linux 6.10-rc2 Linus Torvalds
2024-06-03 7:03 ` Build regressions/improvements in v6.10-rc2 Geert Uytterhoeven
2024-06-08 14:44 ` Linux 6.10-rc2 - massive performance regression David Laight
2024-06-08 16:02 ` Linus Torvalds
2024-06-08 21:35 ` David Laight
2024-06-08 22:00 ` Linus Torvalds
2024-06-08 22:28 ` Woody Suwalski
2024-06-09 8:07 ` Johan Hovold
2024-06-09 8:11 ` Linux regression tracking (Thorsten Leemhuis)
2024-06-09 9:35 ` David Laight [this message]
2024-06-09 14:24 ` David Laight
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=930d66db93814520be94f02ee62a19e6@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®