[dpdk-users] No flow type supported (IP fragmentation) for Mellanox NIC?

Sungho Hong maverickjin88 at gmail.com
Thu Sep 20 21:37:53 CEST 2018


Hello DPDK users,

I was struggling with the packet fragmentation,
since the dpdk application(l3fwd, ip-fragmentation, ip-assemble)  did not
recognized the received packet as the  ipv4 header.

At first, I have crafted my own packets when sending ipv4 headers so I
assumed that I was crafting the packets in a wrong way.

So I have used DPDK-pktgen but dpdk-application (l3fwd, ip-fragmentation,
ip-assemble) did not recognized the ipv4 header.
As the last resort, I have tested the dpdk-testpmd, and found out this in
the status info.

---------------------------------------------------------
-----------------------
********************* Infos for port 1  *********************
MAC address: E4:1D:2D:D9:CB:81
Driver name: net_mlx4
Connect to socket: 1
memory allocation on the socket: 1
Link status: up
Link speed: 10000 Mbps
Link duplex: full-duplex
MTU: 1500
Promiscuous mode: enabled
Allmulticast mode: disabled
Maximum number of MAC addresses: 127
Maximum number of MAC addresses of hash filtering: 0
VLAN offload:
  strip on
  filter on
  qinq(extend) off
No flow type is supported.
Max possible RX queues: 65408
Max possible number of RXDs per queue: 65535
Min possible number of RXDs per queue: 0
RXDs number alignment: 1
Max possible TX queues: 65408
Max possible number of TXDs per queue: 65535
Min possible number of TXDs per queue: 0
TXDs number alignment: 1
testpmd> show port
---------------------------------------------------------
-----------------------


According to DPDK documentation.
in the flow type of the info status of port 1 should show, but mine shows
that no flow type is supported.

---------------------------------------------------------
-----------------------
Supported flow types:
  ipv4-frag
  ipv4-tcp
  ipv4-udp
  ipv4-sctp
  ipv4-other
  ipv6-frag
  ipv6-tcp
  ipv6-udp
  ipv6-sctp
  ipv6-other
  l2_payload
  port
  vxlan
  geneve
  nvgre
------------------------------------------------------
---------------------------

So Is my NIC, Mellanox Connect X-3 does not support IP fragmentation? Or is
there additional configuration that needs to be done?


More information about the users mailing list