DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1308] meson_tests/driver:link_bonding_rssconf_autotest test failed
Date: Wed, 08 Nov 2023 03:33:44 +0000	[thread overview]
Message-ID: <bug-1308-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 6622 bytes --]

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

            Bug ID: 1308
           Summary: meson_tests/driver:link_bonding_rssconf_autotest test
                    failed
           Product: DPDK
           Version: 23.11
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: meson
          Assignee: dev@dpdk.org
          Reporter: songx.jiale@intel.com
  Target Milestone: ---

[Environment]
DPDK version: 
dpdk-23.11-rc2: 2bbad8f974e00552d106c27e1d157a31179ab5ec
Other software versions: name/version for QEMU, OVS, etc. Repeat as required.
OS: Ubuntu 22.04.3 LTS/5.15.0-82-generic
Compiler: gcc version 11.4.0
Hardware platform: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
NIC hardware:
Intel Corporation Ethernet Controller E810-C for SFP [8086:1593] (rev 02)
NIC firmware: 
driver: ice-1.13.0_rc99_4_gb8ad35697
firmware-version: 4.40 0x8001c2f8 1.3492.0

[Test Setup]
1. compile dpdk
CC=gcc meson -Denable_kmods=False -Dlibdir=lib --default-library=static
x86_64-native-linuxapp-gcc
ninja -C x86_64-native-linuxapp-gcc -j 72
2. blind port to vfio-pci
./usertools/dpdk-devbind.py -b vfio-pci 0000:05:00.0 0000:08:00.0
3. launch dpdk-test
/root/dpdk/x86_64-native-linuxapp-gcc/app/dpdk-test -c 0xff --vdev=dma_skeleton
-a 0000:05:00.0 -a 0000:08:00.0
4. start test 
RTE>> link_bonding_rssconf_autotest

[Show the output from the previous commands.]
 + ------------------------------------------------------- +
 + Test Suite : RSS Dynamic Configuration for Bonding Unit Test Suite
 + ------------------------------------------------------- +
 + TestCase [ 0] : test_setup succeeded
Device with port_id=1 already stopped
Device with port_id=2 already stopped
Device with port_id=3 already stopped
Device with port_id=4 already stopped
bond_ethdev_promiscuous_disable(2751) - Failed to disable promiscuous mode for
port 1: Operation not supported
bond_ethdev_promiscuous_disable(2751) - Failed to disable promiscuous mode for
port 2: Operation not supported
bond_ethdev_promiscuous_disable(2751) - Failed to disable promiscuous mode for
port 3: Operation not supported
bond_ethdev_promiscuous_disable(2751) - Failed to disable promiscuous mode for
port 4: Operation not supported
bond_ethdev_allmulticast_disable(2897) - Failed to disable allmulti mode for
port 1: Operation not supported
bond_ethdev_allmulticast_disable(2897) - Failed to disable allmulti mode for
port 2: Operation not supported
bond_ethdev_allmulticast_disable(2897) - Failed to disable allmulti mode for
port 3: Operation not supported
bond_ethdev_allmulticast_disable(2897) - Failed to disable allmulti mode for
port 4: Operation not supported
Ethdev port_id=1 invalid RSS key len: 40, valid value: 0
EAL: Test assert test_propagate line 383 failed: Cannot set members RSS keys
EAL: Test assert test_rss line 467 failed: Propagation test failed
Port 1 must be stopped to allow reset
Port 2 must be stopped to allow reset
Port 3 must be stopped to allow reset
Port 4 must be stopped to allow reset
 + TestCase [ 1] : test_rss failed

[Expected Result]
 + ------------------------------------------------------- +
 + Test Suite : RSS Dynamic Configuration for Bonding Unit Test Suite
 + ------------------------------------------------------- +
 + TestCase [ 0] : test_setup succeeded
Device with port_id=1 already stopped
Device with port_id=2 already stopped
Device with port_id=3 already stopped
Device with port_id=4 already stopped
bond_ethdev_promiscuous_disable(2751) - Failed to disable promiscuous mode for
port 1: Operation not supported
bond_ethdev_promiscuous_disable(2751) - Failed to disable promiscuous mode for
port 2: Operation not supported
bond_ethdev_promiscuous_disable(2751) - Failed to disable promiscuous mode for
port 3: Operation not supported
bond_ethdev_promiscuous_disable(2751) - Failed to disable promiscuous mode for
port 4: Operation not supported
bond_ethdev_allmulticast_disable(2897) - Failed to disable allmulti mode for
port 1: Operation not supported
bond_ethdev_allmulticast_disable(2897) - Failed to disable allmulti mode for
port 2: Operation not supported
bond_ethdev_allmulticast_disable(2897) - Failed to disable allmulti mode for
port 3: Operation not supported
bond_ethdev_allmulticast_disable(2897) - Failed to disable allmulti mode for
port 4: Operation not supported
bond_ethdev_rss_hash_update(3208) - rss_key will be truncated
bond_ethdev_rss_hash_update(3208) - rss_key will be truncated
bond_ethdev_rss_hash_update(3208) - rss_key will be truncated
bond_ethdev_rss_hash_update(3208) - rss_key will be truncated
bond_ethdev_rss_hash_update(3208) - rss_key will be truncated
bond_ethdev_rss_hash_update(3208) - rss_key will be truncated
bond_ethdev_rss_hash_update(3208) - rss_key will be truncated
bond_ethdev_rss_hash_update(3208) - rss_key will be truncated
bond_ethdev_rss_hash_update(3208) - rss_key will be truncated

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

commit bae3cfa520a7205d63752c506d51e832d4944180
Author: Jie Hai <haijie1@huawei.com>
Date:   Thu Nov 2 16:20:12 2023 +0800

    ethdev: clarify RSS related fields usage

    In rte_eth_dev_rss_hash_conf_get(), the "rss_key_len" should be
    greater than or equal to the "hash_key_size" which get from
    rte_eth_dev_info_get() API. And the "rss_key" should contain at
    least "hash_key_size" bytes. If these requirements are not met,
    the query unreliable.

    In rte_eth_dev_rss_hash_update() or rte_eth_dev_configure(), the
    "rss_key_len" indicates the length of the "rss_key" in bytes of
    the array pointed by "rss_key", it should be equal to the
    "hash_key_size" if "rss_key" is not NULL.

    This patch overwrites the comments of fields of "rte_eth_rss_conf"
    and "RTE_ETH_HASH_FUNCTION_DEFAULT", checks "rss_key_len" in
    ethdev level, and documents these changes.

    Signed-off-by: Jie Hai <haijie1@huawei.com>
    Acked-by: Huisong Li <lihuisong@huawei.com>
    Acked-by: Chengwen Feng <fengchengwen@huawei.com>
    Reviewed-by: Ferruh Yigit <ferruh.yigit@amd.com>

 doc/guides/rel_notes/release_23_11.rst |  5 +++++
 lib/ethdev/rte_ethdev.c                | 31 +++++++++++++++++++++++++++++++
 lib/ethdev/rte_ethdev.h                | 33 ++++++++++++++++++---------------
 lib/ethdev/rte_flow.h                  |  1 +
 4 files changed, 55 insertions, 15 deletions

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

[-- Attachment #2: Type: text/html, Size: 8900 bytes --]

             reply	other threads:[~2023-11-08  3:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08  3:33 bugzilla [this message]
2023-11-10  2:09 ` 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-1308-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).