Re: [dpdk-dev] [RFC v2] net/mlx5: support new naming scheme for representors

2019-03-05 Thread Dekel Peled
Thanks, PSB. > -Original Message- > From: Stephen Hemminger > Sent: Monday, March 4, 2019 9:14 PM > To: Dekel Peled > Cc: Shahaf Shuler ; Yongseok Koh > ; dev@dpdk.org; Ori Kam ; > Matan Azrad > Subject: Re: [dpdk-dev] [RFC v2] net/mlx5: support new naming s

Re: [dpdk-dev] [RFC v2] net/mlx5: support new naming scheme for representors

2019-03-04 Thread Stephen Hemminger
On Sun, 3 Mar 2019 07:14:07 + Dekel Peled wrote: > In current kernel implementation, the physical port name for representors is > a numeric string (i.e. '0', '1', etc.). > > > > Kernel patch [1] implements an updated scheme for naming of representors > ports. > > The new scheme gives a

[dpdk-dev] [RFC v2] net/mlx5: support new naming scheme for representors

2019-03-02 Thread Dekel Peled
In current kernel implementation, the physical port name for representors is a numeric string (i.e. '0', '1', etc.). Kernel patch [1] implements an updated scheme for naming of representors ports. The new scheme gives a unique name for each port using the PF ID and the VF ID. Uplink represent