From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1132] net/i40e changes recommended Rx ring_size after device start
Date: Wed, 23 Nov 2022 08:57:13 +0000 [thread overview]
Message-ID: <bug-1132-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1132
Bug ID: 1132
Summary: net/i40e changes recommended Rx ring_size after device
start
Product: DPDK
Version: 22.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: andrew.rybchenko@oktetlabs.ru
Target Milestone: ---
net/i40e changes recommended Rx ring_size after device start
NIC is Intel X710
It does not make sense since all Rx queues are typically already configured and
started.
It happens because of link_speeds condition above:
790 »·······} else {
3791 »·······»·······/* For X710 */
3792 »·······»·······dev_info->speed_capa = RTE_ETH_LINK_SPEED_1G |
RTE_ETH_LINK_SPEED_10G;
3793 »·······»·······dev_info->default_rxportconf.nb_queues = 1;
3794 »·······»·······dev_info->default_txportconf.nb_queues = 1;
3795 »·······»·······if (dev->data->dev_conf.link_speeds &
RTE_ETH_LINK_SPEED_10G) {
3796 »·······»·······»·······dev_info->default_rxportconf.ring_size = 512;
3797 »·······»·······»·······dev_info->default_txportconf.ring_size = 256;
3798 »·······»·······} else {
3799 »·······»·······»·······dev_info->default_rxportconf.ring_size = 256;
3800 »·······»·······»·······dev_info->default_txportconf.ring_size = 256;
3801 »·······»·······}
3802 »·······}
which are updated on device start in i40e_apply_link_speed().
Before start default_rxportconf.ring_size is 256, after start it is 512.
Found using [1]
[1]
https://ts-factory.io/doc/dpdk-ethdev-ts/generated/rst/group_usecases-dev_info_persistence.html#doxid-group-usecases-dev-info-persistence
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-11-23 8:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 8:57 bugzilla [this message]
2022-11-30 7:35 ` 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-1132-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).