[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4ecddff0-5ba4-51f7-1544-3d76d43b6b39@mellanox.com>
Date: Wed, 27 Nov 2019 13:20:17 +0000
From: Paul Blakey <paulb@...lanox.com>
To: wenxu <wenxu@...oud.cn>
CC: "pablo@...filter.org" <pablo@...filter.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Mark Bloch <markb@...lanox.com>
Subject: Re: Question about flow table offload in mlx5e
On 11/27/2019 3:11 PM, Paul Blakey wrote:
> On 11/27/2019 2:16 PM, wenxu wrote:
>
>> Sorry maybe something mess you, Ignore with my patches.
>>
>>
>> I also did the test like you with route tc rules to ft callback.
>>
>>
>> please also did the following test: mlx_p0 is the pf and mlx_pf0vf0
>> is the vf .
>>
> Are you in switchdev mode (via devlink) or default legacy mode?
>
>
mlx_pf0vf0 is representor device created after entring switchdev mode? and eth0 in vm is the binded mlx5 VF?
Can you run this command:
sudo grep -ri "" /sys/class/net/*/phys_* 2>/dev/null
example:
/sys/class/net/ens1f0_0/phys_port_name:pf0vf0
/sys/class/net/ens1f0_0/phys_switch_id:b828a50003078a24
/sys/class/net/ens1f0_1/phys_port_name:pf0vf1
/sys/class/net/ens1f0_1/phys_switch_id:b828a50003078a24
/sys/class/net/ens1f0/phys_port_name:p0
/sys/class/net/ens1f0/phys_switch_id:b828a50003078a24
and
sudo ls /sys/class/net/*/device/virtfn*/net
example:
/sys/class/net/ens1f0/device/virtfn0/net:
ens1f2
/sys/class/net/ens1f0/device/virtfn1/net:
ens1f3
and even
lspci | grep -i mellanox ; ls -l /sys/class/net
Thansk.
Powered by blists - more mailing lists