From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 17F2B2A5D for ; Wed, 9 Aug 2017 11:00:55 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Aug 2017 02:00:54 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.41,346,1498546800"; d="scan'208";a="888133944" Received: from irsmsx153.ger.corp.intel.com ([163.33.192.75]) by FMSMGA003.fm.intel.com with ESMTP; 09 Aug 2017 02:00:47 -0700 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.220]) by IRSMSX153.ger.corp.intel.com ([169.254.9.74]) with mapi id 14.03.0319.002; Wed, 9 Aug 2017 10:00:44 +0100 From: "De Lara Guarch, Pablo" To: "Yang, Zhiyong" , "dev@dpdk.org" CC: "thomas@monjalon.net" Thread-Topic: [dpdk-dev] [PATCH 0/2] increase port_id range Thread-Index: AQHTEOt4irPXrnVcrU62vmjX5qgvRKJ7ubSQ Date: Wed, 9 Aug 2017 09:00:43 +0000 Message-ID: References: <20170809084203.17562-1-zhiyong.yang@intel.com> In-Reply-To: <20170809084203.17562-1-zhiyong.yang@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 10.0.102.7 dlp-reaction: no-action x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH 0/2] increase port_id range X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Aug 2017 09:00:56 -0000 Hi Zhiyong, > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Zhiyong Yang > Sent: Wednesday, August 9, 2017 9:42 AM > To: dev@dpdk.org > Cc: thomas@monjalon.net > Subject: [dpdk-dev] [PATCH 0/2] increase port_id range >=20 > 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. >=20 > It is necessary for a redefinition of port_id to extend it from 1 bytes t= o > 2 bytes. All ethdev APIs and usages related to port_id will be changed at= the > same time. >=20 > Below is an API/ABI change notice for DPDK 17.11. > http://www.dpdk.org/dev/patchwork/patch/27475/ >=20 > Discussion about port_id is the following thread. > http://www.dpdk.org/dev/patchwork/patch/23208/ >=20 > Zhiyong Yang (2): > ethdev: increase port_id range > examples: increase port_id range >=20 > app/pdump/main.c | 2 +- > app/test-pmd/cmdline.c | 4 +- > app/test-pmd/testpmd.c | 4 +- > app/test-pmd/testpmd.h | 2 +- > drivers/net/bonding/rte_eth_bond.h | 40 ++-- > drivers/net/bonding/rte_eth_bond_8023ad.c | 6 +- > drivers/net/bonding/rte_eth_bond_api.c | 54 +++--- > drivers/net/bonding/rte_eth_bond_pmd.c | 10 +- > drivers/net/bonding/rte_eth_bond_private.h | 36 ++-- > drivers/net/failsafe/failsafe_ether.c | 4 +- > drivers/net/failsafe/failsafe_private.h | 4 +- > drivers/net/ring/rte_eth_ring.c | 2 +- > examples/bond/main.c | 6 +- > examples/ip_fragmentation/main.c | 4 +- > examples/l3fwd-power/main.c | 7 +- > examples/l3fwd/l3fwd.h | 10 +- > examples/l3fwd/l3fwd_em.c | 2 +- > examples/l3fwd/l3fwd_lpm.c | 2 +- > examples/link_status_interrupt/main.c | 5 +- > examples/performance-thread/l3fwd-thread/main.c | 7 +- > examples/rxtx_callbacks/main.c | 8 +- > lib/librte_ether/rte_ethdev.c | 231 +++++++++++-------= ----- > lib/librte_ether/rte_ethdev.h | 236 ++++++++++++------= ------ > lib/librte_ether/rte_tm.c | 62 +++---- > lib/librte_ether/rte_tm.h | 60 +++--- > lib/librte_ether/rte_tm_driver.h | 2 +- > lib/librte_latencystats/rte_latencystats.c | 8 +- > lib/librte_pdump/rte_pdump.c | 16 +- > lib/librte_pdump/rte_pdump.h | 4 +- > lib/librte_port/rte_port_ethdev.c | 6 +- > lib/librte_port/rte_port_ethdev.h | 6 +- > 31 files changed, 431 insertions(+), 419 deletions(-) >=20 > -- > 2.13.3 You should remove the deprecation notice that was sent for the ABI breakage in this patchset, and add a note in release notes, documenting the API/ABI changes that you have done. Thanks, Pablo