From: Erik Gabriel Carrillo <erik.g.carrillo@intel.com>
To: john.mcnamara@intel.com
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] doc: update release notes for timer library changes
Date: Mon, 6 May 2019 16:29:56 -0500 [thread overview]
Message-ID: <1557178196-26569-1-git-send-email-erik.g.carrillo@intel.com> (raw)
Message-ID: <20190506212956.fRpc_gEvs_Q5w2E24KM4AQa3USUVybTPaDNwSCxotnQ@z> (raw)
Signed-off-by: Erik Gabriel Carrillo <erik.g.carrillo@intel.com>
---
doc/guides/rel_notes/release_19_05.rst | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/doc/guides/rel_notes/release_19_05.rst b/doc/guides/rel_notes/release_19_05.rst
index 5044ac7..f4457ac 100644
--- a/doc/guides/rel_notes/release_19_05.rst
+++ b/doc/guides/rel_notes/release_19_05.rst
@@ -266,6 +266,11 @@ API Changes
* power: ``rte_power_set_env`` and ``rte_power_unset_env`` functions
have been modified to be thread safe.
+* timer: Functions have been introduced that allow multiple instances of the
+ timer lists to be created, and they are now allocated in shared memory. New
+ functions allow particular timer lists to be selected when timers are being
+ started, stopped, and managed.
+
ABI Changes
-----------
@@ -296,6 +301,9 @@ ABI Changes
alignment for ``rte_crypto_asym_op`` to restore expected ``rte_crypto_op``
layout and alignment.
+* timer: ``rte_timer_subsystem_init`` now returns success or failure to reflect
+ whether it was able to allocate memory.
+
Shared Library Versions
-----------------------
--
2.6.4
next reply other threads:[~2019-05-06 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 21:29 Erik Gabriel Carrillo [this message]
2019-05-06 21:29 ` Erik Gabriel Carrillo
2019-05-07 15:32 ` Mcnamara, John
2019-05-07 15:32 ` Mcnamara, John
2019-05-09 22:19 ` Thomas Monjalon
2019-05-09 22:19 ` Thomas Monjalon
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=1557178196-26569-1-git-send-email-erik.g.carrillo@intel.com \
--to=erik.g.carrillo@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.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;
as well as URLs for NNTP newsgroup(s).