From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1127] net/i40e does not preserve RSS redirection table upon port stop/start
Date: Thu, 17 Nov 2022 08:09:35 +0000 [thread overview]
Message-ID: <bug-1127-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1127
Bug ID: 1127
Summary: net/i40e does not preserve RSS redirection table upon
port stop/start
Product: DPDK
Version: 22.07
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: andrew.rybchenko@oktetlabs.ru
CC: ivan.malov@oktetlabs.ru
Target Milestone: ---
net/i40e does not preserve RSS redirection table upon port stop/start
lib/ethdev/rte_ethdev.h line 86:
79 * Please note that some configuration is not stored between calls to
80 * rte_eth_dev_stop()/rte_eth_dev_start(). The following configuration
will
81 * be retained:
82 *
83 * - MTU
84 * - flow control settings
85 * - receive mode configuration (promiscuous mode, all-multicast mode,
86 * hardware checksum mode, RSS/VMDq settings etc.)
87 * - VLAN filtering configuration
88 * - default MAC address
89 * - MAC addresses supplied to MAC address array
90 * - flow director filtering mode (but not filtering rules)
91 * - NIC queue statistics mappings
defines that RSS settings must be retained across restart.
Example log from dpdk-ethdev-ts tests available [1]. Lines below are lines in
the log.
Steps to reproduce should be trivial and as far as I know testpmd has all
required functionality:
- configure more than 1 Rx queue,
- start port (line 38),
- update reta (lines 41 and 43),
- stop (line 72),
- start again (line 74),
- read reta (line 77) and compare (example log shows that RETA is reset to
default).
Obviously update should not match default configuration.
[1]
https://ts-factory.io/bublik/v2/log/189828?focusId=190450&mode=treeAndinfoAndlog
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2022-11-17 8:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-1127-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).