Hi Matej,

-----Original Message-----
From: Matej Vido [mailto:vido@cesnet.cz]
Sent: Wednesday, September 13, 2017 4:14 PM
To: Yigit, Ferruh <redacted>; Yang, Zhiyong
[off-list ref]; dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 0/4] increase port_id range

On 11.09.2017 12:23, Ferruh Yigit wrote:

quoted

On 9/9/2017 3:47 PM, Zhiyong Yang wrote:

quoted

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!

Regarding the szedata2 PMD this change is fine.

Thanks for your review. 
Zhiyong

Thanks,
Matej