All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhiyong Yang <zhiyong.yang@intel.com>
To: dev@dpdk.org, zhihong.wang@intel.com
Cc: john.mcnamara@intel.com, oilvier.matz@6wind.com,
	thomas@monjalon.net, Zhiyong Yang <zhiyong.yang@intel.com>
Subject: [PATCH] doc: announce API and ABI change for ethdev
Date: Wed, 12 Jul 2017 15:58:46 +0800	[thread overview]
Message-ID: <20170712075846.14834-1-zhiyong.yang@intel.com> (raw)

  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 devices 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.

Signed-off-by: Zhiyong Yang <zhiyong.yang@intel.com>
---
 doc/guides/rel_notes/deprecation.rst | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 257dcba..f265980 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -54,6 +54,10 @@ 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 the "rte_eth_dev_data" structure.
+  Change the definition of port_id from 8bits to 16bits in order to support
+  more than 256 devices in DPDK.
+
 * 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.9.3

             reply	other threads:[~2017-07-12  7:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-12  7:58 Zhiyong Yang [this message]
2017-08-04  1:12 ` [PATCH] doc: announce API and ABI change for ethdev 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 ` [PATCH v2] " Zhiyong Yang
2017-08-04  6:56   ` 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   ` [PATCH v3] " Zhiyong Yang
2017-08-08  4:02     ` Yang, Zhiyong
2017-08-08  9:35       ` 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=20170712075846.14834-1-zhiyong.yang@intel.com \
    --to=zhiyong.yang@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=oilvier.matz@6wind.com \
    --cc=thomas@monjalon.net \
    --cc=zhihong.wang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.