From: Jean-Baptiste Roquefere <jb.roquefere@ateme.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: K Prateek Nayak <kprateek.nayak@amd.com>,
Peter Zijlstra <peterz@infradead.org>,
"mingo@kernel.org" <mingo@kernel.org>,
Juri Lelli <juri.lelli@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Borislav Petkov <bp@alien8.de>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
"Gautham R. Shenoy" <gautham.shenoy@amd.com>,
Swapnil Sapkal <swapnil.sapkal@amd.com>,
Valentin Schneider <vschneid@redhat.com>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: IPC drop down on AMD epyc 7702P
Date: Fri, 23 May 2025 12:24:13 +0000 [thread overview]
Message-ID: <fea6da1d-85d6-459d-9ac3-661d5909420b@ateme.com> (raw)
In-Reply-To: <CAKfTPtDkmsFD=1uG+dGOrYfdaap4SWupc8kVV8LanwaXSbxruA@mail.gmail.com>
Hello Vincent,
> As said previously, I don't see an obvious connection between commit
> 16b0a7a1a0af ("sched/fair: Ensure tasks spreading in LLC during LB")
> which mainly ensures a better usage of CPUs inside a LLC. Do you have
> cpufreq and freq scaling enabled ? The only link that I could think
> of, is that the spread of task inside a llc favors inter LLC newly
> idle load balance
# lsmod | grep cpufreq
cpufreq_userspace 16384 0
cpufreq_conservative 16384 0
cpufreq_powersave 16384 0
but I'm not sure cpufreq is well loaded :
# cpupower frequency-info
analyzing CPU 0:
no or unknown cpufreq driver is active on this CPU
CPUs which run at the same hardware frequency: Not Available
CPUs which need to have their frequency coordinated by software: Not
Available
maximum transition latency: Cannot determine or is not supported.
Not Available
available cpufreq governors: Not Available
Unable to determine current policy
current CPU frequency: Unable to call hardware
current CPU frequency: Unable to call to kernel
boost state support:
Supported: yes
Active: yes
Boost States: 0
Total States: 3
Pstate-P0: 2000MHz
Pstate-P1: 1800MHz
Pstate-P2: 1500MHz
And I cant find cpufreq/ under /sys/devices/system/cpu/cpu*/
Thanks for your help,
jb
next prev parent reply other threads:[~2025-05-23 12:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 21:08 Jean-Baptiste Roquefere
2025-04-18 6:39 ` K Prateek Nayak
2025-04-28 7:43 ` Jean-Baptiste Roquefere
2025-04-30 9:13 ` K Prateek Nayak
2025-04-30 9:25 ` Peter Zijlstra
2025-04-30 10:41 ` Libo Chen
2025-04-30 11:29 ` K Prateek Nayak
2025-05-01 2:46 ` Libo Chen
2025-05-05 10:28 ` Vincent Guittot
2025-05-05 12:29 ` K Prateek Nayak
2025-05-05 15:10 ` Vincent Guittot
2025-05-05 15:16 ` K Prateek Nayak
2025-05-16 15:05 ` Jean-Baptiste Roquefere
2025-05-22 14:51 ` Vincent Guittot
2025-05-23 12:24 ` Jean-Baptiste Roquefere [this message]
2025-05-26 7:53 ` Vincent Guittot
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=fea6da1d-85d6-459d-9ac3-661d5909420b@ateme.com \
--to=jb.roquefere@ateme.com \
--cc=bp@alien8.de \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=gautham.shenoy@amd.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=regressions@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=swapnil.sapkal@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®