[dpdk-dev] [Bug 832] flow_classify_softnic/inconsistent_rules: create rule failed

[dpdk-dev] [Bug 832] flow_classify_softnic/inconsistent_rules: create rule failed

[bugzilla]

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

            Bug ID: 832
           Summary: flow_classify_softnic/inconsistent_rules: create rule
                    failed
           Product: DPDK
           Version: 21.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: leweix.yang@intel.com
  Target Milestone: ---

Environment


DPDK version: Use make showversion or for a non-released version: git remote -v
&& git show-ref --heads
21.11.0-rc0:f4acb429d09db0594d41c5f5a48906df03ce6e5c
Other software versions: name/version for QEMU, OVS, etc. Repeat as required.
OS: Red Hat Enterprise Linux 8.4 4.18.0-305.19.1.el8_4.x86_64 
Compiler: gcc (GCC) 8.4.1 20200928 (Red Hat 8.4.1-1)
Hardware platform: Intel(R) Xeon(R) Gold 6252N CPU @ 2.30GHz.
NIC hardware: Ethernet Controller XXV710 for 25GbE SFP28 158b
Device version: 2.17.1
NIC firmware: 8.30 0x8000a485 1.2926.0


Test Setup
Steps to reproduce
List the steps to reproduce the issue:

1. build dpdk 
# rm -rf x86_64-native-linuxapp-gcc
# CC=gcc meson --werror -Denable_kmods=True -Dlibdir=lib
-Dc_args='-DRTE_EAL_IGB_UIO=1' --default-library=static
x86_64-native-linuxapp-gcc 
# ninja -C x86_64-native-linuxapp-gcc -j 70 
2. lanch app
# x86_64-native-linuxapp-gcc/app/dpdk-testpmd  --vdev
'net_softnic0,firmware=./drivers/net/softnic/flow_classify_softnic/flow_ipv4_addr_hash_firmware.cli,cpu_id=1,conn_port=8086'
-l
1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95
-n 4 -a 0000:af:00.0 -a 0000:af:00.1  --file-prefix=dpdk_56223_20211022105747  
-s 0x4 -- -i --rxq=2 --txq=2 --disable-rss --portmask=0x4
3. creat rule
# flow create 4 group 0 ingress pattern eth / ipv4 proto mask 0 src mask
0.0.0.0 dst mask 255.255.255.255 src spec 100.0.0.1 dst spec 200.0.0.1 proto
spec 17 / udp src mask 0 dst mask 0 src spec 100 dst spec 200 / end actions
queue index 3 / end


Show the output from the previous commands:

#testpmd> flow create 4 group 0 ingress pattern eth / ipv4 proto mask 0 src
mask 0.0.0.0 dst mask 255.255.255.255 src spec 100.0.0.1 dst spec 200.0.0.1
proto spec 17 / udp src mask 0 dst mask 0 src spec 100 dst spec 200 / end
actions queue index 3 / end
Invalid port 4


Expected Result
Explain what is the expected result in text or as an example output:

# create rule success



Regression
Is this issue a regression: (Y/N) Y 

git show 1179f05cc9a044541106981b0366f474043d7872
commit 1179f05cc9a044541106981b0366f474043d7872 (HEAD)
Author: Ivan Malov <ivan.malov@oktetlabs.ru>
Date: Thu Oct 14 06:21:45 2021 +0300

ethdev: query proxy port to manage transfer flows

Not all DPDK ports in a given switching domain may have the
privilege to manage "transfer" flows. Add an API to find a
port with sufficient privileges by any port in the domain.

Signed-off-by: Ivan Malov <ivan.malov@oktetlabs.ru>
Reviewed-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Acked-by: Ori Kam <orika@nvidia.com>

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

[dpdk-dev] [Bug 832] flow_classify_softnic/inconsistent_rules: create rule failed

[bugzilla]

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

jiang,yu (yux.jiang@intel.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |yux.jiang@intel.com
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #2 from jiang,yu (yux.jiang@intel.com) ---
Not a defect, display changes based on bad commit it.

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