From mboxrd@z Thu Jan 1 00:00:00 1970 From: Remy Horton Subject: Re: [PATCH v2] doc: announce API and ABI change for ethdev Date: Fri, 4 Aug 2017 07:56:18 +0100 Message-ID: <61ed8dc6-99f1-cfb5-a560-ac4d2f0a6657@intel.com> References: <20170712075846.14834-1-zhiyong.yang@intel.com> <20170804052753.35535-1-zhiyong.yang@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: jianfeng.tan@intel.com, yliu@fridaylinux.org, jerin.jacob@caviumnetworks.com, thomas@monjalon.net To: Zhiyong Yang , dev@dpdk.org Return-path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 3675B2C18 for ; Fri, 4 Aug 2017 08:56:21 +0200 (CEST) In-Reply-To: <20170804052753.35535-1-zhiyong.yang@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 04/08/2017 06:27, Zhiyong Yang wrote: > 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. I think this reads a little better: This is an API/ABI change notice for DPDK 17.11 announcing the redefinition of port_id. port_id is currently defined as uint8_t, which is limited to the range 0 to 255. A larger range is required for vdev scalability. It is necessary for a redefinition of port_id to extend it from 1 bytes to 2 bytes. All ethdev APIs and usages related to port_id will be changed at the same time. > doc/guides/rel_notes/deprecation.rst | 6 ++++++ > 1 file changed, 6 insertions(+) Acked-by: Remy Horton