From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1310] iavf : max_rtx_queues not true when network adaptor not support large vf
Date: Thu, 09 Nov 2023 07:43:38 +0000 [thread overview]
Message-ID: <bug-1310-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1654 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1310
Bug ID: 1310
Summary: iavf : max_rtx_queues not true when network adaptor
not support large vf
Product: DPDK
Version: 22.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: yue.ma@ericsson.com
Target Milestone: ---
our app code use dev_info->max_tx_queues to check the max queue.
we get dev_info->max_rx_queues=265(IAVF_MAX_NUM_QUEUES_LV), but when we try to
requet 30 tx queue, we got iavf_dev_configure(): large VF is not supported.
by check code we find that :
max queue number of nomal vf is 16 (IAVF_MAX_NUM_QUEUES_DFLT).
may be the code need to change like this :
drivers/net/iavf/iavf_ethdev.c:
static int
iavf_dev_info_get(struct rte_eth_dev *dev, struct rte_eth_dev_info *dev_info)
{
struct iavf_adapter *adapter =
IAVF_DEV_PRIVATE_TO_ADAPTER(dev->data->dev_private);
struct iavf_info *vf = &adapter->vf;
if (adapter->closed)
return -EIO;
dev_info->max_rx_queues = IAVF_MAX_NUM_QUEUES_LV;
dev_info->max_tx_queues = IAVF_MAX_NUM_QUEUES_LV;
+ if (vf->vf_res->vf_cap_flags & VIRTCHNL_VF_LARGE_NUM_QPAIRS){
+ dev_info->max_rx_queues = IAVF_MAX_NUM_QUEUES_DFLT;
+ dev_info->max_tx_queues = IAVF_MAX_NUM_QUEUES_DFLT;
+ }
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3577 bytes --]
reply other threads:[~2023-11-09 7:43 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-1310-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).