[dpdk-users] using rte_flow via tespmd with Intel X552

Adrien Mazarguil adrien.mazarguil at 6wind.com
Fri Apr 14 11:22:02 CEST 2017


Hi Tetsuro,

On Thu, Apr 13, 2017 at 10:18:28AM +0900, Tetsuro Nakamura wrote:
> Hi All,
> 
> I'm now trying to use simple L2 function with "Generic Flow API (rte_flow)"
> using testpmd in dpdk-17.02,
> but it doesn't work with the error below.
> 
> -----------
> $sudo ./dpdk-17.02/x86_64-native-linuxapp-gcc/app/testpmd -l 0-3 -n 4 -- -i
> --portmask=0x3 --nb-cores=2
> 
> testpmd> flow validate 0 ingress pattern eth / eth dst is a0:36:9f:78:30:26
> / end actions drop / end
> Caught error type 9 (specific pattern item): cause: 0x7ffd225adc88, Not
> supported by L2 tunnel filter
> testpmd> flow validate 0 ingress pattern eth / eth dst is a0:36:9f:78:30:26
> / end actions queue index 0 / end
> Caught error type 9 (specific pattern item): cause: 0x7ffd225adc88, Not
> supported by L2 tunnel filter
> -----------
> 
> I tried several other flows and got the same error.
> I'm using Intel X552 NIC. The firmware-version is 0x800003e7.
> 
> -----------
> $ sudo ethtool -i rename6
> driver: ixgbe
> version: 5.0.4
> firmware-version: 0x800003e7
> expansion-rom-version:
> bus-info: 0000:03:00.0
> supports-statistics: yes
> supports-test: yes
> supports-eeprom-access: yes
> supports-register-dump: yes
> supports-priv-flags: no
> -----------
> 
> My question is,
> am I missing some additional settings to do ?
> Should I use another firmware version ?
> # DPDK 17.02 official release note says the tested firmware version was
> 0x800001cf.
> # My version, 0x800003e7 is newer, isn't it?
> 
> I don't think the NIC does't support such simple L2 functions.
> But if it doesn't, are there any documents that tell us which NIC supports
> which flow rules in rte_flow?
> Could you tell me what flows I can try with Intel X552 NIC?
> 
> Thank you and best regards,
> 
> Tetsuro Nakamura, NTT

I'm not familiar with ixgbe but this issue reminds me of this thread [1],
particularly the following comment:

 "the rte_flow_error returned was not very useful for it does return the
 error of the last tried filter-type (L2 tunnel in ixgbe), and not the error
 of the filter-type that my setup should use (flow director)"

CC'ing Wenzhuo, I think this issue is present in 17.02, has it been fixed
since?

[1] http://dpdk.org/ml/archives/dev/2017-March/059928.html

-- 
Adrien Mazarguil
6WIND


More information about the users mailing list