From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1129] net/mlx5: cannot transmit if Tx queue is setup with maximum number of descriptors
Date: Thu, 17 Nov 2022 12:52:20 +0000 [thread overview]
Message-ID: <bug-1129-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1129
Bug ID: 1129
Summary: net/mlx5: cannot transmit if Tx queue is setup with
maximum number of descriptors
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/mlx5: cannot transmit if Tx queue is setup with maximum number of
descriptors
net/mlx5 does not report Rx/Tx descriptors limits (min/max/align).
As the result application sees theoretical maximum UINT16_MAX (65535) which is
set as the default by ethdev.
If application tries to use the value to setup Tx queue, setup succeed, but Tx
burst always returns 0. I guess the reason is in the following log message:
mlx5_net: port 0 increased number of descriptors in Tx queue 0 to the next
power of two (0)
i.e. effective number of descriptors is equal to 0.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2022-11-17 12:52 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-1129-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).