From: Hajkowski <marcinx.hajkowski@intel.com>
To: david.hunt@intel.com
Cc: dev@dpdk.org, Marcin Hajkowski <marcinx.hajkowski@intel.com>
Subject: [dpdk-dev] [PATCH 0/4] rte_power APIs enhancement
Date: Fri, 15 Mar 2019 10:34:16 +0100 [thread overview]
Message-ID: <20190315093420.9812-1-marcinx.hajkowski@intel.com> (raw)
From: Marcin Hajkowski <marcinx.hajkowski@intel.com>
Modifications to assure thread safety of rte_power APIs for
power env set and unset, better user notification by returning more
suitable value and internal data cleaning corrections.
Marcin Hajkowski (4):
power: fix non thread-safe power env modification
power: return error in set env when power env already set
power: reset function pointers on unset env
power: add UTs for all power env types
app/test/test_power.c | 155 +++++++++++++++++++------
doc/guides/rel_notes/release_19_05.rst | 6 +
lib/librte_power/rte_power.c | 52 +++++++--
lib/librte_power/rte_power.h | 3 +-
4 files changed, 170 insertions(+), 46 deletions(-)
--
2.17.2
next reply other threads:[~2019-03-15 9:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 9:34 Hajkowski [this message]
2019-03-15 9:34 ` Hajkowski
2019-03-15 9:34 ` [dpdk-dev] [PATCH 1/4] power: fix non thread-safe power env modification Hajkowski
2019-03-15 9:34 ` Hajkowski
2019-03-15 9:34 ` [dpdk-dev] [PATCH 2/4] power: return error in set env when power env already set Hajkowski
2019-03-15 9:34 ` Hajkowski
2019-03-15 9:34 ` [dpdk-dev] [PATCH 3/4] power: reset function pointers on unset env Hajkowski
2019-03-15 9:34 ` Hajkowski
2019-03-15 9:34 ` [dpdk-dev] [PATCH 4/4] power: add UTs for all power env types Hajkowski
2019-03-15 9:34 ` Hajkowski
-- strict thread matches above, loose matches on Subject: below --
2019-03-13 19:48 [dpdk-dev] [PATCH 0/4] rte_power APIs enhancement Hajkowski
2019-03-13 19:48 ` Hajkowski
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=20190315093420.9812-1-marcinx.hajkowski@intel.com \
--to=marcinx.hajkowski@intel.com \
--cc=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).