From: Stephen Hemminger <stephen@networkplumber.org>
To: stable@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH 22.11] power: increase the number of UNCORE frequencies
Date: Wed, 24 Jul 2024 10:55:19 -0700 [thread overview]
Message-ID: <20240724175542.75520-1-stephen@networkplumber.org> (raw)
[ upstream commit 93db1cfcc36ac1808c4a09ec50a470c6127b859e ]
The number of lcore frequencies was too low for some CPU's.
This lead to standalone test failures.
Fixes: 60b8a661a957 ("power: add Intel uncore frequency control")
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
app/test/test_power_intel_uncore.c | 2 +-
lib/power/rte_power_intel_uncore.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/app/test/test_power_intel_uncore.c b/app/test/test_power_intel_uncore.c
index 31163af84e..38c72fb371 100644
--- a/app/test/test_power_intel_uncore.c
+++ b/app/test/test_power_intel_uncore.c
@@ -17,7 +17,7 @@ test_power_intel_uncore(void)
#include <rte_power_intel_uncore.h>
#include <power_common.h>
-#define MAX_UNCORE_FREQS 32
+#define MAX_UNCORE_FREQS 64
#define VALID_PKG 0
#define VALID_DIE 0
diff --git a/lib/power/rte_power_intel_uncore.c b/lib/power/rte_power_intel_uncore.c
index 3b8724385f..7193b86516 100644
--- a/lib/power/rte_power_intel_uncore.c
+++ b/lib/power/rte_power_intel_uncore.c
@@ -11,7 +11,7 @@
#include "rte_power_intel_uncore.h"
#include "power_common.h"
-#define MAX_UNCORE_FREQS 32
+#define MAX_UNCORE_FREQS 64
#define MAX_NUMA_DIE 8
#define BUS_FREQ 100000
#define FILTER_LENGTH 18
--
2.43.0
next reply other threads:[~2024-07-24 17:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 17:55 Stephen Hemminger [this message]
2024-07-25 8:30 ` Luca Boccassi
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=20240724175542.75520-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).