[dpdk-dev] [PATCH v3 0/4] increase port_id range
zhiyong.yang at intel.com
Mon Sep 11 13:25:26 CEST 2017
> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Monday, September 11, 2017 6:23 PM
> To: Yang, Zhiyong <zhiyong.yang at intel.com>; dev at dpdk.org
> Cc: thomas at monjalon.net; hemant.agrawal at nxp.com; Hunt, David
> <david.hunt at intel.com>
> Subject: Re: [PATCH v3 0/4] increase port_id range
> 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
> PMD Maintainers, please review this patch for your PMD, this innocent uint8_t
> to uint16_t change may break your PMD!
Agreed seriously. The patchset needs more reviews and comments.
More information about the dev