From: Zhiyong Yang <zhiyong.yang@intel.com>
To: dev@dpdk.org
Cc: jianfeng.tan@intel.com, yliu@fridaylinux.org,
jerin.jacob@caviumnetworks.com, thomas@monjalon.net,
Zhiyong Yang <zhiyong.yang@intel.com>
Subject: [dpdk-dev] [PATCH v2] doc: announce API and ABI change for ethdev
Date: Fri, 4 Aug 2017 13:27:53 +0800 [thread overview]
Message-ID: <20170804052753.35535-1-zhiyong.yang@intel.com> (raw)
In-Reply-To: <20170712075846.14834-1-zhiyong.yang@intel.com>
This is an API/ABI change notice for DPDK 17.11 on redefinition of
port_id. port_id is defined as uint8_t by now, which is just ranged
from 0 to 255. For more and more scenerioes, more than 256 ports are
needed to support for vdev scalability.
It is necessary for redefinition of port_id to extend from 1 bytes
to 2 bytes. All ethdev APIs and use cases related to port_id will be
changed at the same time.
cc: jianfeng.tan@intel.com
cc: yliu@fridaylinux.org
cc: jerin.jacob@caviumnetworks.com
cc: thomas@monjalon.net
Signed-off-by: Zhiyong Yang <zhiyong.yang@intel.com>
Acked-by: Jianfeng Tan <jianfeng.tan@intel.com>
Acked-by: Yuanhan Liu <yliu@fridaylinux.org>
Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
---
Change in V2.
1. remove indent of paragraph in commit log.
2. add more description about API/ABI according to yuanhan's comments.
doc/guides/rel_notes/deprecation.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 72aa40495..4edaf92fb 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -49,6 +49,12 @@ Deprecation Notices
Target release for removal of the legacy API will be defined once most
PMDs have switched to rte_flow.
+* ABI/API changes are planned for 17.11 in all structures which include port_id
+ definition such as "rte_eth_dev_data", "rte_port_ethdev_reader_params",
+ "rte_port_ethdev_writer_params", and so on. The definition of port_id will be
+ changed from 8 bits to 16 bits in order to support more than 256 ports in
+ DPDK. All APIs which have port_id parameter will be changed at the same time.
+
* librte_table: The ``key_mask`` parameter will be added to all the hash tables
that currently do not have it, as well as to the hash compute function prototype.
The non-"do-sig" versions of the hash tables will be removed
--
2.13.3
next prev parent reply other threads:[~2017-08-04 5:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 7:58 [dpdk-dev] [PATCH] " Zhiyong Yang
2017-08-04 1:12 ` Tan, Jianfeng
2017-08-04 4:07 ` Yuanhan Liu
2017-08-04 4:13 ` Jerin Jacob
2017-08-04 5:36 ` Yang, Zhiyong
2017-08-04 5:27 ` Zhiyong Yang [this message]
2017-08-04 6:56 ` [dpdk-dev] [PATCH v2] " Remy Horton
2017-08-05 10:34 ` Yang, Zhiyong
2017-08-07 3:07 ` Yang, Zhiyong
2017-08-07 11:04 ` Thomas Monjalon
2017-08-07 15:20 ` Shahaf Shuler
2017-08-07 12:42 ` [dpdk-dev] [PATCH v3] " Zhiyong Yang
2017-08-08 4:02 ` Yang, Zhiyong
2017-08-08 9:35 ` Thomas Monjalon
-- strict thread matches above, loose matches on Subject: below --
2017-01-05 10:44 [dpdk-dev] [PATCH v1] " Bernard Iremonger
2017-01-05 15:25 ` [dpdk-dev] [PATCH v2] " Bernard Iremonger
2017-02-13 17:57 ` Thomas Monjalon
2017-02-14 3:17 ` Jerin Jacob
2017-02-14 10:33 ` Iremonger, Bernard
2017-02-14 19:37 ` 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=20170804052753.35535-1-zhiyong.yang@intel.com \
--to=zhiyong.yang@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=jianfeng.tan@intel.com \
--cc=thomas@monjalon.net \
--cc=yliu@fridaylinux.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).