From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 398] MLX5 device won't start with no RX queue
Date: Thu, 13 Feb 2020 10:56:08 +0000 [thread overview]
Message-ID: <bug-398-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=398
Bug ID: 398
Summary: MLX5 device won't start with no RX queue
Product: DPDK
Version: 19.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: srn@nexatech.fr
Target Milestone: ---
When using a mlx5 device as TX only (0 rx queue), the call to rte_eth_dev_start
fails with the following message:
net_mlx5: port 1 cannot allocate RSS queue list (0)
net_mlx5: port 1 reta config failed: Cannot allocate memory
From what I see in the code it's because, in mlx5_dev_start(), the very first
thing that is called without condition is mlx5_dev_configure_rss_reta(), which
immediately tries to malloc(nb_rx_queus*blablabla), which returns 0 because
requested size is 0.
My dirty fix is, in mlx5_dev_configure_rss_reta
(drivers/net/mlx5/mlx5_ethdev.c):
- if (priv->skip_default_rss_reta == 0)
+ if (priv->skip_default_rss_reta || rxqs_n == 0)
return ret;
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-02-13 10:56 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-398-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).