Re: [dpdk-dev] [PATCH v6 0/5] increase port_id range

2017-10-11 Thread Yang, Zhiyong
Hi ferruh, > >> Zhiyong Yang (5): > >> net/bonding: remove bonding APIs using ABI versioning > >> ethdev: increase port_id range > >> examples: increase port_id range > >> test: increase port_id range > >> librte_mbuf: modify port initialization value > > > > Series applied to dpdk-next-

Re: [dpdk-dev] [PATCH v6 0/5] increase port_id range

2017-10-11 Thread Ferruh Yigit
On 10/6/2017 3:15 AM, Ferruh Yigit wrote: > On 9/29/2017 8:17 AM, 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 by

Re: [dpdk-dev] [PATCH v6 0/5] increase port_id range

2017-10-06 Thread Thomas Monjalon
06/10/2017 04:15, Ferruh Yigit: > On 9/29/2017 8:17 AM, Zhiyong Yang wrote: > > Zhiyong Yang (5): > > net/bonding: remove bonding APIs using ABI versioning > > ethdev: increase port_id range > > examples: increase port_id range > > test: increase port_id range > > librte_mbuf: modify port

Re: [dpdk-dev] [PATCH v6 0/5] increase port_id range

2017-10-06 Thread Thomas Monjalon
06/10/2017 04:15, Ferruh Yigit: > On 9/29/2017 8:17 AM, 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

Re: [dpdk-dev] [PATCH v6 0/5] increase port_id range

2017-10-06 Thread Gaëtan Rivet
On Fri, Oct 06, 2017 at 03:15:40AM +0100, Ferruh Yigit wrote: > On 9/29/2017 8:17 AM, 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

Re: [dpdk-dev] [PATCH v6 0/5] increase port_id range

2017-10-05 Thread Ferruh Yigit
On 9/29/2017 8:17 AM, 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 relat

[dpdk-dev] [PATCH v6 0/5] increase port_id range

2017-09-29 Thread Zhiyong Yang
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. Dis