From: Bruce Richardson <bruce.richardson@intel.com>
To: Robin Jarry <rjarry@redhat.com>
Cc: <dev@dpdk.org>, Vladimir Medvedkin <vladimir.medvedkin@intel.com>,
"Beilei Xing" <beilei.xing@intel.com>,
Ting Xu <ting.xu@intel.com>, <stable@dpdk.org>
Subject: Re: [PATCH dpdk] iavf: fix reported max TX and RX queues in ethdev info
Date: Fri, 9 Jan 2026 14:25:52 +0000 [thread overview]
Message-ID: <aWEP8FqWsDVvwzK6@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20260109142129.1550058-2-rjarry@redhat.com>
On Fri, Jan 09, 2026 at 03:21:30PM +0100, Robin Jarry wrote:
> With a regular iavf device, rte_eth_dev_info_get reports 256 maximum TX
> and RX queues. Trying to configure a port with 20 queues returns an
> error:
>
> ERR: IAVF_DRIVER: iavf_dev_configure(): large VF is not supported
>
> When the large VF feature isn't supported by the PF kernel driver,
> ethdev info must not report 256 supported queues but 16.
>
> Fixes: e436cd43835b ("net/iavf: negotiate large VF and request more queues")
> Cc: stable@dpdk.org
>
> Signed-off-by: Robin Jarry <rjarry@redhat.com>
> ---
> drivers/net/intel/iavf/iavf_ethdev.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/intel/iavf/iavf_ethdev.c b/drivers/net/intel/iavf/iavf_ethdev.c
> index 15e49fe24814..59328ebc5ad2 100644
> --- a/drivers/net/intel/iavf/iavf_ethdev.c
> +++ b/drivers/net/intel/iavf/iavf_ethdev.c
> @@ -1126,12 +1126,18 @@ 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;
> + uint16_t max_queue_pairs;
>
> 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)
> + max_queue_pairs = IAVF_MAX_NUM_QUEUES_LV;
> + else
> + max_queue_pairs = IAVF_MAX_NUM_QUEUES_DFLT;
> +
> + dev_info->max_rx_queues = max_queue_pairs;
> + dev_info->max_tx_queues = max_queue_pairs;
> dev_info->min_rx_bufsize = IAVF_BUF_SIZE_MIN;
> dev_info->max_rx_pktlen = IAVF_FRAME_SIZE_MAX;
> dev_info->max_mtu = dev_info->max_rx_pktlen - IAVF_ETH_OVERHEAD;
> --
Makes sense.
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
prev parent reply other threads:[~2026-01-09 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 14:21 Robin Jarry
2026-01-09 14:25 ` Bruce Richardson [this message]
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=aWEP8FqWsDVvwzK6@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=rjarry@redhat.com \
--cc=stable@dpdk.org \
--cc=ting.xu@intel.com \
--cc=vladimir.medvedkin@intel.com \
/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).