From: Konstantin Ananyev <konstantin.ananyev@intel.com>
To: dev@dpdk.org
To: dev@dpdk.org
Cc: Konstantin Ananyev <konstantin.ananyev@intel.com>
Subject: [dpdk-dev] [RFC PATCH 3/3] doc: ethdev ABI change deprecation notice
Date: Fri, 1 Dec 2017 14:48:02 +0000 [thread overview]
Message-ID: <1512139682-11114-4-git-send-email-konstantin.ananyev@intel.com> (raw)
In-Reply-To: <1512139682-11114-1-git-send-email-konstantin.ananyev@intel.com>
Signed-off-by: Konstantin Ananyev <konstantin.ananyev@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 13e85432f..038b55fd5 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -8,6 +8,11 @@ API and ABI deprecation notices are to be posted here.
Deprecation Notices
-------------------
+* ethdev: an ABI changes for ``rte_ethdev`` are planned in v18.05.
+ The size and layout of struct rte_eth_dev will change.
+ Mainly to accommodate queue specific RX/TX function pointers, plus
+ reorganize RX/TX callback related information.
+
* eal: several API and ABI changes are planned for ``rte_devargs`` in v18.02.
The format of device command line parameters will change. The bus will need
to be explicitly stated in the device declaration. The enum ``rte_devtype``
--
2.13.5
next prev parent reply other threads:[~2017-12-01 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 14:47 [dpdk-dev] [RFC PATCH 0/3] *** SUBJECT HERE *** Konstantin Ananyev
2017-12-01 14:48 ` [dpdk-dev] [RFC PATCH 1/3] ethdev: introduce eth_queue_local Konstantin Ananyev
2017-12-01 14:48 ` [dpdk-dev] [RFC PATCH 2/3] ethdev: make it safe to remove rx/tx callback at runtime Konstantin Ananyev
2017-12-01 14:48 ` Konstantin Ananyev [this message]
2017-12-12 14:55 ` [dpdk-dev] [RFC PATCH 3/3] doc: ethdev ABI change deprecation notice Kovacevic, Marko
2017-12-01 14:56 ` [dpdk-dev] [RFC PATCH 0/3] *** SUBJECT HERE *** Ananyev, Konstantin
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=1512139682-11114-4-git-send-email-konstantin.ananyev@intel.com \
--to=konstantin.ananyev@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).