DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1048] [dpdk-22.07rc3] i40e_rss_input/flow_query: RSS types is not displayed tests failed
Date: Thu, 07 Jul 2022 06:15:51 +0000	[thread overview]
Message-ID: <bug-1048-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 1048
           Summary: [dpdk-22.07rc3] i40e_rss_input/flow_query: RSS types
                    is not displayed tests failed
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: testpmd
          Assignee: dev@dpdk.org
          Reporter: weiyuanx.li@intel.com
  Target Milestone: ---

[Environment]
DPDK version: Use make showversion or for a non-released version: git remote -v
&& git show-ref --heads
 dpdk22.07-rc3: 204638154ea1ce7682ca4124b78520247ed0c0a8
OS: Red Hat Enterprise Linux 8.4 (Ootpa)/4.18.0-305.19.1.el8_4.x86_64
Compiler: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-4)
Hardware platform: Intel(R) Xeon(R) Gold 6252N CPU @ 2.30GHz
NIC hardware: Ethernet Controller XXV710 for 25GbE SFP28 158b
NIC firmware: 
driver: i40e
version: 2.19.3
firmware-version:  8.70 0x8000c3eb 1.3179.0

[Test Setup]
Steps to reproduce
List the steps to reproduce the issue.

1. bind PF to vfio-pci
usertools/dpdk-devbind.py --force --bind=vfio-pci 0000:af:00.0 0000:af:00.1

2. start pmd
x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 1-4 -n 4 -a 0000:af:00.0 
--file-prefix=dpdk_2946122_20220707104711     -- -i --portmask=0x1 --rxq=4
--txq=4

3. input command in testpmd

set verbose 8
set fwd rxonly
start
flow create 0 ingress pattern eth / ipv4 / tcp / end actions rss types ipv4-tcp
end queues end / end
flow create 0 ingress pattern eth / ipv4 / udp / end actions rss types ipv4-udp
l3-src-only end queues end func symmetric_toeplitz / end
flow create 0 ingress pattern end actions rss types end queues end func
simple_xor / end
flow create 0 ingress pattern end actions rss types end queues 1 2 end / end

flow query 0 0 rss

[show the output]
testpmd> flow query 0 0 rss
RSS:
 queues: none
 function: default
 types:

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

testpmd> flow query 0 0 rss
RSS:
 queues: none
 function: default
 types:
  ipv4-tcp 

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

534988c490f1d50c935602e0ef83cc17a055feef is the first bad commit
commit 534988c490f1d50c935602e0ef83cc17a055feef
Author: Huisong Li <lihuisong@huawei.com>
Date:   Wed Jun 29 16:34:48 2022 +0800

    app/testpmd: unify RSS types display

    The 'rss_type_table[]' maintains the name and value of RSS types. This
    patch unifies a common interface to display RSS types.

    Signed-off-by: Huisong Li <lihuisong@huawei.com>
    Signed-off-by: Ferruh Yigit <ferruh.yigit@xilinx.com>

 app/test-pmd/config.c | 34 ++++++++++++++++++++--------------
 1 file changed, 20 insertions, 14 deletions

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

             reply	other threads:[~2022-07-07  6:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07  6:15 bugzilla [this message]
2022-07-13  7:19 ` bugzilla

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-1048-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).