From: Harry van Haaren <harry.van.haaren@intel.com>
To: dev@dpdk.org
Cc: maryam.tahhan@intel.com, Harry van Haaren <harry.van.haaren@intel.com>
Subject: [dpdk-dev] [PATCH] doc: announce xstats api change for 16.07
Date: Tue, 5 Apr 2016 18:58:09 +0100 [thread overview]
Message-ID: <1459879089-3430-1-git-send-email-harry.van.haaren@intel.com> (raw)
This patch adds a notice that the API for the xstats
functionality will be modified in the 16.07 release, with
no backwards compatibility planned as it would require
code duplication in each PMD that supports xstats.
Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
---
doc/guides/rel_notes/deprecation.rst | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 98d5529..13c3a95 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -54,3 +54,8 @@ Deprecation Notices
induce a modification of the rte_mempool structure, plus a
modification of the API of rte_mempool_obj_iter(), implying a breakage
of the ABI.
+
+* ABI change is planned for the xstats API and rte_eth_xstats struct, to
+ facilitate updating to an API that allows retrieval of values without any
+ string copies or parsing. No backwards compatibility is planned, as it would
+ require code duplication in every PMD that supports xstats.
--
2.5.0
next reply other threads:[~2016-04-05 17:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 17:58 Harry van Haaren [this message]
2016-04-05 18:45 ` Thomas Monjalon
2016-04-06 9:02 ` Van Haaren, Harry
2016-04-06 9:22 ` Thomas Monjalon
2016-04-06 11:16 ` Van Haaren, Harry
2016-04-06 12:14 ` Thomas Monjalon
2016-04-06 13:49 ` David Harton (dharton)
2016-04-06 13:53 ` Van Haaren, Harry
2016-04-06 13:46 ` Remy Horton
2016-04-06 14:00 ` David Harton (dharton)
2016-04-06 14:25 ` Tahhan, Maryam
2016-04-07 21:36 ` 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=1459879089-3430-1-git-send-email-harry.van.haaren@intel.com \
--to=harry.van.haaren@intel.com \
--cc=dev@dpdk.org \
--cc=maryam.tahhan@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).