[dpdk-dev] [Bug 565] [dpdk-20.11]metering_and_policing/test_ipv4_HASH_table_RFC2698: create rule failed

[dpdk-dev] [Bug 565] [dpdk-20.11]metering_and_policing/test_ipv4_HASH_table_RFC2698: create rule failed

[bugzilla]

https://bugs.dpdk.org/show_bug.cgi?id=565

            Bug ID: 565
           Summary: [dpdk-20.11]metering_and_policing/test_ipv4_HASH_table
                    _RFC2698: create rule failed
           Product: DPDK
           Version: 20.11
          Hardware: All
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: testpmd
          Assignee: dev@dpdk.org
          Reporter: junx.w.zhou@intel.com
  Target Milestone: ---

Environment
Fill in all the following as completely as possible. Use "Unknown" or "N/A" if
required. Use {{braces}} to create fixed width text like this: braces.



DPDK version: Use make showversion or for a non-released version: git remote -v
&& git show-ref --heads
 20.11-rc1 4669252e0421aaf06ff86d5339f970ebe72cbf22
Other software versions: name/version for QEMU, OVS, etc. Repeat as required.
OS: Ubuntu 20.04.1 LTS/5.4.0-42-generic
Compiler: gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Hardware platform: Intel(R) Xeon(R) Gold 6139 CPU @ 2.30GHz
NIC hardware: Fortville_25g
NIC firmware: 
driver: i40e
version: 2.13.10
firmware-version: 8.00 0x80008c1a 1.2766.0
Test Setup
Steps to reproduce
List the steps to reproduce the issue.

1.usertools/dpdk-devbind.py --force --bind=vfio-pci 0000:86:00.0 0000:86:00.1
2.cp /root/dpdk/drivers/net/softnic/meter_and_policing_firmware.cli
/root/dpdk/drivers/net/softnic/meter_and_policing_firmware.cli-7
3.sed -i -e 's/^.*link LINK0 dev.*$/link LINK0 dev 0000:86:00.0/g'
/root/dpdk/drivers/net/softnic/meter_and_policing_firmware.cli-7
4.sed -i -e 's/^.*link LINK1 dev.*$/link LINK1 dev 0000:86:00.1/g'
/root/dpdk/drivers/net/softnic/meter_and_policing_firmware.cli-7
5.sed -i -e 's/^.*table action profile AP0.*$/table action profile AP0 ipv4
offset 270 fwd meter trtcm tc 1 stats pkts/g'
/root/dpdk/drivers/net/softnic/meter_and_policing_firmware.cli-7
6.sed -i -e 's/^.*pipeline RX table match.*$/pipeline RX table match hash ext
key 16 mask 00FF0000FFFFFFFFFFFFFFFFFFFFFFFF offset 278 buckets 16K size 65K
action AP0/g' /root/dpdk/drivers/net/softnic/meter_and_policing_firmware.cli-7
7.sed -i -e 's/thread 5 pipeline RX enable/thread 2 pipeline RX enable/g'
/root/dpdk/drivers/net/softnic/meter_and_policing_firmware.cli-7
8.sed -i -e 's/thread 5 pipeline TX enable/thread 2 pipeline TX enable/g'
/root/dpdk/drivers/net/softnic/meter_and_policing_firmware.cli-7
9.x86_64-native-linuxapp-gcc/app/dpdk-testpmd  -c 0x7 -s 0x4 -n 4 --vdev
'net_softnic0,firmware=/root/dpdk/drivers/net/softnic/meter_and_policing_firmware.cli-7'
         -- -i  --rxq=2 --txq=2 --portmask=0x4 --disable-rss
10.another session: sudo ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x7 -s 0x4
-n 4 --vdev
'net_softnic0,firmware=/root/dpdk/drivers/net/softnic/meter_and_policing_firmware.cli,cpu_id=0,conn_port=8086'
-- -i --forward-mode=softnic --rxq=2 --txq=2 --portmask=0x4
11.add port meter profile trtcm_rfc2698 2 0 3125000000 3125000000 400 500
12.create port meter 2 0 0 yes g y r 0 0 0
13.flow create 2 group 0 ingress pattern eth / ipv4 proto mask 255 src mask
255.255.255.255 dst mask 255.255.255.255 src spec 1.10.11.12 dst spec
2.20.21.22 proto spec 6 / tcp src mask 65535 dst mask 65535 src spec 2 dst spec
2 / end actions meter mtr_id 0 / queue index 0 / end
            dut.10.240.183.197:
port_flow_complain(): Caught PMD error type 1 (cause unspecified): HASH: Item
list is not observing the match format: Invalid argument
Show the output from the previous commands.

flow create 2 group 0 ingress pattern eth / ipv4 proto mask 255 src mask
255.255.255.255 dst mask 255.255.255.255 src spec 1.10.11.12 dst spec
2.20.21.22 proto spec 6 / tcp src mask 65535 dst mask 65535 src spec 2 dst spec
2 / end actions meter mtr_id 0 / queue index 0 / end dut.10.240.183.197:
port_flow_complain(): Caught PMD error type 1 (cause unspecified): HASH: Item
list is not observing the match format: Invalid argument
Expected Result
Explain what is the expected result in text or as an example output:

no error log
Regression
Is this issue a regression: (Y)

Version the regression was introduced: 

commit 09315fc83861ada1119b7ebdb258877ec68e6bd7
Author: Dekel Peled <dekelp@nvidia.com>
Date: Thu Oct 15 18:51:46 2020 +0300

ethdev: add VLAN attributes to ethernet and VLAN items

This patch implements the change proposes in RFC [1], adding dedicated
fields to ETH and VLAN items structs, to clearly define the required
characteristic of a packet, and enable precise match criteria.
Documentation is updated accordingly.

[1] https://mails.dpdk.org/archives/dev/2020-August/177536.html

Signed-off-by: Dekel Peled <dekelp@nvidia.com>
Acked-by: Matan Azrad <matan@nvidia.com>
Acked-by: Ori Kam <orika@nvidia.com>

Stack Trace or Log
flow create 2 group 0 ingress pattern eth / ipv4 proto mask 255 src mask
255.255.255.255 dst mask 255.255.255.255 src spec 1.10.11.12 dst spec
2.20.21.22 proto spec 6 / tcp src mask 65535 dst mask 65535 src spec 2 dst spec
2 / end actions meter mtr_id 0 / queue index 0 / end dut.10.240.183.197:
port_flow_complain(): Caught PMD error type 1 (cause unspecified): HASH: Item
list is not observing the match format: Invalid argument

-- 
You are receiving this mail because:
You are the assignee for the bug.