From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH v3 0/4] increase port_id range Date: Mon, 11 Sep 2017 11:26:44 +0100 Message-ID: <951fd16f-2f2f-e079-fcd3-d5cddef1ba7d@intel.com> References: <20170904055734.21354-1-zhiyong.yang@intel.com> <20170909144727.46388-1-zhiyong.yang@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: thomas@monjalon.net, hemant.agrawal@nxp.com, david.hunt@intel.com To: Zhiyong Yang , dev@dpdk.org Return-path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 6692C6D45 for ; Mon, 11 Sep 2017 12:26:47 +0200 (CEST) In-Reply-To: <20170909144727.46388-1-zhiyong.yang@intel.com> Content-Language: en-US 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 9/9/2017 3:47 PM, Zhiyong Yang wrote: > 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. > > Discussion about port_id is the following thread. > http://www.dpdk.org/dev/patchwork/patch/23208/ > > Changes in V2: > 1. cover more PMDs to increase port_id range. > 2. cover more examples to increase port_id range. > 3. add 17.11 release note. > > Changes in V3: > 1. cover mlx4 and mlx5. > 2. add to increase port_id range in test code. > 3. The patch "librte_mbuf: modify port initialization value" is merged > into the patchset. > > Zhiyong Yang (4): > ethdev: increase port_id range > test: increase port_id range > examples: increase port_id range > librte_mbuf: modify port initialization value This breaks almost all rte_eth_dev APIs, and will effect almost all users! So please document this update in release notes. Thanks, ferruh