Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Jean-Baptiste Roquefere <jb.roquefere@ateme.com>
To: K Prateek Nayak <kprateek.nayak@amd.com>,
	Vincent Guittot <vincent.guittot@linaro.org>
Cc: 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, 16 May 2025 15:05:55 +0000	[thread overview]
Message-ID: <db7b5ad7-3dad-4e7c-a323-d0128ae818eb@ateme.com> (raw)
In-Reply-To: <c0e87c08-f863-47f3-8016-c44e3dce2811@amd.com>

Hello Prateek,
long time no see... I've been very busy lately.

Did he try with relax_domain_level=3, i.e. prevent newilde idle


>> balance between LLC ? I don't see results showing that it's not enough
>> to prevent newly idle migration between LLC
>
> I don't think he did. JB if it isn't too much trouble, could you please
> try running with "relax_domain_level=3" in kernel cmdline and see if
> the performance is similar to "relax_domain_level=2".

I just tried relax_domain_level=3 on my payload. As you can see 
relax_domain_level=3 performances are more or less the same

+--------------------+---------------------+---------------------+
| Kernel             | 6.12.17 relax dom 2 | 6.12.17 relax dom 3 |
+--------------------+---------------------+---------------------+
| Utilization (%)    | 52,01               | 52,15 |
| CPU effective freq | 1 294,12            | 1 309,85 |
| IPC                | 1,42                | 1,40 |
| L2 access (pti)    | 38,18               | 38,03 |
| L2 miss   (pti)    | 7,78                | 7,90 |
| L3 miss   (abs)    | 33 929 609 924,00   | 33 705 899 797,00 |
| Mem (GB/s)         | 49,10               | 48,91 |
| Context switches   | 107 896 729,00      | 106 441 463,00 |
| CPU migrations     | 16 075 947,00       | 18 129 700,00 |
| Real time (s)      | 193,39              | 193,41 |
+--------------------+---------------------+---------------------+

We got the point that tuning this variable is not a good solution, but 
for now it's the only one we can apply.

Without this tuning our solution loses real time video processing. With 
: we keep real time on.


Thanks for your help, I'll stay alert on this thread if someday a better 
solution can emerge.


Regards,


jb


  reply	other threads:[~2025-05-16 15:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17 21:08 IPC drop down on AMD epyc 7702P 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 [this message]
2025-05-22 14:51                 ` Vincent Guittot
2025-05-23 12:24                   ` Jean-Baptiste Roquefere
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=db7b5ad7-3dad-4e7c-a323-d0128ae818eb@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