From: David Hunt <david.hunt@intel.com>
To: dev@dpdk.org
Cc: david.hunt@intel.com
Subject: [PATCH] lib/power: power pmd errata with RTM and gcc-9
Date: Wed, 9 Mar 2022 13:22:21 +0000 [thread overview]
Message-ID: <20220309132221.18210-1-david.hunt@intel.com> (raw)
An errata exists where users may see reduced power savings when using
PMD Power Management. This issue occurs when compiling DPDK applications
with gcc-9 on platforms with TSX enabled. In rte_power_monitor_multi(),
the function may return without successfully starting the RTM
transaction (the _xbegin() fails).
Signed-off-by: David Hunt <david.hunt@intel.com>
---
doc/guides/rel_notes/release_22_03.rst | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/doc/guides/rel_notes/release_22_03.rst b/doc/guides/rel_notes/release_22_03.rst
index 60e5b4f9aa..34d6f34dba 100644
--- a/doc/guides/rel_notes/release_22_03.rst
+++ b/doc/guides/rel_notes/release_22_03.rst
@@ -313,6 +313,17 @@ Known Issues
Also, make sure to start the actual text at the margin.
=======================================================
+* **Possible reduced power saving with PMD Power Management.**
+
+ Users may see reduced power savings when using PMD Power Management.
+ This issue occurs when compiling DPDK applications with gcc-9 on
+ platforms with TSX enabled. In rte_power_monitor_multi(), the
+ function may return without successfully starting the RTM
+ transaction (the _xbegin() fails).
+
+ There are three workarounds for this issue. Either build DPDK with gcc-11
+ or newer, build with shared libraries, or build DPDK with fewer drivers.
+
Tested Platforms
----------------
--
2.17.1
next reply other threads:[~2022-03-09 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 13:22 David Hunt [this message]
2022-03-16 19:44 ` Thomas Monjalon
2022-03-22 16:11 ` David Hunt
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=20220309132221.18210-1-david.hunt@intel.com \
--to=david.hunt@intel.com \
--cc=dev@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).