https://bugs.dpdk.org/show_bug.cgi?id=403
Bug ID: 403
Summary: i40e: cannot add 2 rte_flows with one matching TCP
sport and the other dport
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: maxime.le...@6wind.com
Target Milestone: ---
With dpdk master (commit id d0e160a00233), I got the following error when I try
to create one rte_flow matching TCP dport and one matching TCP sport:
./build/app/testpmd --legacy-mem -c 1f -n 4 -w 0000:85:00.1 -- -i --rxq=1
--txq=1 --total-num-mbufs=10000
EAL: Detected 40 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Static memory layout is selected, amount of reserved memory can be
adjusted with -m or --socket-mem
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: No available hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: PCI device 0000:85:00.1 on NUMA socket 1
EAL: probe driver: 8086:1583 net_i40e
EAL: using IOMMU type 1 (Type 1)
Interactive-mode selected
...
testpmd> flow create 0 ingress pattern eth / ipv4 / tcp dst is 179 / end
actions queue index 0 / end
Flow rule #0 created
testpmd> flow create 0 ingress pattern eth / ipv4 / tcp src is 180 / end
actions queue index 0 / end
port_flow_complain(): Caught PMD error type 13 (specific pattern item): cause:
0x2001582a0, Conflict with the first rule's input set.: Invalid argument
The message error is not very useful. Because these rules doesn't conflict.
These rules are working perfectly fine with other nic. Is It an hardware
limitation or a software limitation ?
Are there any documentation to know what is supported by the i40e nic with
rte_flow API ?
--
You are receiving this mail because:
You are the assignee for the bug.
