From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 215135] proposed cpufreq driver amd-pstate regresses wrt acpi-cpufreq on some AMD EPYC Zen3
Date: Tue, 18 Jan 2022 09:54:10 +0000 [thread overview]
Message-ID: <bug-215135-137361-ZPGNwyGILG@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215135-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215135
Joe (jinzhou.su@amd.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jinzhou.su@amd.com
--- Comment #2 from Joe (jinzhou.su@amd.com) ---
Hello Giovanni,
Thanks for testing AMD Pstate driver. Finally we have set up the same device on
our local, here is the lscpu info:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 256
On-line CPU(s) list: 0-255
Thread(s) per core: 2
Core(s) per socket: 64
Socket(s): 2
NUMA node(s): 2
Vendor ID: AuthenticAMD
CPU family: 25
Model: 1
Here is the tbench test result.
acpi-cpufreq-ondemand 17628 MB/sec ( 1.00)
acpi-cpufreq-perfgov 25317 MB/sec ( 1.43)
acpi-cpufreq-sugov 21369 MB/sec ( 1.21)
amd-pstate-ondemand 17913 MB/sec ( 1.02)
amd-pstate-perfgov 25865 MB/sec ( 1.47)
amd-pstate-sugov 22359 MB/sec ( 1.26)
From our site of view, amd-pstate performs slight better acpi driver in
Tbench4. The test based on 50 times test in each policy.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-01-18 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 13:41 [Bug 215135] New: proposed cpufreq driver amd-pstate regresses wrt acpi-cpufreq on some AMD EPYC Zen3 bugzilla-daemon
2021-11-25 13:47 ` [Bug 215135] " bugzilla-daemon
2022-01-18 9:54 ` bugzilla-daemon [this message]
2022-06-24 1:24 ` bugzilla-daemon
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=bug-215135-137361-ZPGNwyGILG@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-pm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.