Re: [dpdk-dev] [PATCH 1/2] common/mlx5: share kernel interface name getter

2020-06-18 Thread Matan Azrad
Yes, more conflict are exists with current master-net-mlx. I have newest version rebased on master-net-mlx. I will send new version, for all the old versions... > -Original Message- > From: Maxime Coquelin > Sent: Thursday, June 18, 2020 7:07 PM > To: Matan Azrad ; Slava Ovsiienko > > C

Re: [dpdk-dev] [PATCH 1/2] common/mlx5: share kernel interface name getter

2020-06-18 Thread Maxime Coquelin
Your series does not apply, there are no common ancestor so I can't do 3-way merge. Could you please rebase it on top of next-virtio's master branch? Thanks, Maxime On 6/2/20 5:53 PM, Matan Azrad wrote: > Some configuration of the mlx5 port are done by the kernel net device > associated to the I

Re: [dpdk-dev] [PATCH 1/2] common/mlx5: share kernel interface name getter

2020-06-18 Thread Maxime Coquelin
On 6/2/20 5:53 PM, Matan Azrad wrote: > Some configuration of the mlx5 port are done by the kernel net device > associated to the IB device represents the PCI device. > > The DPDK mlx5 driver uses linux system calls, for example ioctl, in > order to configure per port configurations requested b

[dpdk-dev] [PATCH 1/2] common/mlx5: share kernel interface name getter

2020-06-02 Thread Matan Azrad
Some configuration of the mlx5 port are done by the kernel net device associated to the IB device represents the PCI device. The DPDK mlx5 driver uses linux system calls, for example ioctl, in order to configure per port configurations requested by the DPDK user. One of the basic knowledges requi