jrfastab / match-interface Goto Github PK

There is no way to configure CutThruMode for FM10000 series.

This is what I have: 2 PCs running Linux 4.4.13, each with a FM10420 card, produced by Silicom.
I loaded the driver fm10k-0.21.7 from sourceforge, IES version 4.3 and latest version of match-interfaces.
I have a configuration file fm_platform_attributes.cfg of which I'm confident it is complete.

The goal is to be able to send traffic between the 2 PCs using the FM10420 cards at 100Gbps.
I managed to get the link up on both sides, when I send packets from one side, the tx_packets gets incremented but the peer does not see the packets (even its rx_packets counter won't increase).
The traffic sent between the 2 PCs is ARP.

Please provide some hints on what should be the simplest / correct process.
I would prefer to use the fm10k driver embedded in Linux kernel tree to avoid using UIO.

Thanks in advance for any pointers.

I am testing Intel FM10000 with match-interface.
I setup a VF interface enp133s0f1 (lport 50000) on a fm10k host interface enp133s0 (port 3), then I sent packets with dst mac as mac of enp133s0f1 from another server.
If the packet is vlan untagged, it can be captured on enp133s0f1 with tcpdump.
If the packet is vlan tagged (vlan=100), it can’t be captured on enp133s0f1, but it can be captured on enp133s0.
I have set port 3 vlan as below:

[root@test09 ~]# match get_ports min 3 max 3
port 3:
state: up
speed: 40G
max_frame_size: 15360
type:
loopback: disabled
learning: disabled
update_dscp: enabled
update_ttl: enabled
mcast_flooding: enabled
update_dmac: enabled
update_smac: disabled
update_vlan: enabled
vlan:
default vlan: 1
default priority: 0
drop tagged: disabled
drop untagged: disabled
vlan membership: 1 100
stats:
rx_packets 71
rx_bytes 11894
rx_unicast_packets 0
rx_multicast_packets 48
rx_broadcast_packets 23
rx_unicast_bytes 0
rx_multicast_bytes 3936
rx_broadcast_bytes 7958
tx_packets 54
tx_bytes 16580
tx_unicast_packets 1
tx_multicast_packets 7
tx_broadcast_packets 46
tx_unicast_bytes 102
tx_multicast_bytes 562
tx_broadcast_bytes 15916
[root@test09 ~]#

Then I found the VF vlan membership is not set:

[root@test09 ~]# match phys_port_lookup lport 50000
port 50000:
state:
speed:
phys_id: 3
type:
glort: 0x4000
vlan:
default vlan: 0
default priority: 0
vlan membership:
stats:
rx_packets 0
rx_bytes 0
rx_unicast_packets 0
rx_multicast_packets 0
rx_broadcast_packets 0
rx_unicast_bytes 0
rx_multicast_bytes 0
rx_broadcast_bytes 0
tx_packets 0
tx_bytes 0
tx_unicast_packets 0
tx_multicast_packets 0
tx_broadcast_packets 0
tx_unicast_bytes 0
tx_multicast_bytes 0
tx_broadcast_bytes 0
[root@test09 ~]#

I doubt that is why vlan tagged packets can't reach the VF, but it seems that match-interface doesn't support VF port configuration:

[root@test09 ~]# match set_port port 50000
Warning: received cmd without valid attribute expected 10
Error: match_nl_get_ports failed

what's more, there is no way to check the VF port statistics with match-interface.

Can anybody help?