From: "Wu, Yanglong" <yanglong.wu@intel.com>
To: "Wu, Yanglong" <yanglong.wu@intel.com>,
"Dai, Wei" <wei.dai@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4] net/ixgbe: fix l3fwd start failed on VF
Date: Thu, 11 Jan 2018 15:29:23 +0000 [thread overview]
Message-ID: <B73B41DFFD120A45AEE57672FCA463BA0195C845@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <B73B41DFFD120A45AEE57672FCA463BA0195C6C7@shsmsx102.ccr.corp.intel.com>
Hi daiwei:
After I double checked with this bug, the problem can be described as follow:
When we start PF using testpmd like this: testpmd -c 0x3 -n 4 --socket-mem=1024,1024 --file-prefix=pf -w 0000:05:00.0 -w 0000:05:00.1 -- -i. The number of queue signed to each port would be 1 and the rxmode.mq_mode of ixgbe eth_dev would be set as ETH_MQ_RX_NONE. And this config info is make sense, so until now there is no problem, right?
And according to the code:
case ETH_MQ_RX_NONE:
> /* if nothing mq mode configure, use default scheme */
> dev->data->dev_conf.rxmode.mq_mode = ETH_MQ_RX_VMDQ_ONLY;
> - if (RTE_ETH_DEV_SRIOV(dev).nb_q_per_pool > 1)
> - RTE_ETH_DEV_SRIOV(dev).nb_q_per_pool = 1;
> break;
The nb_q_per_pool of (RTE_ETH_DEV_SRIOV(dev).nb_q_per_pool would be set as 1, that means for VF the number of max queue can be used would be only 1.
And next we start VF using l3fwd:
l3fwd/build/l3fwd -c 0xc0000 -n 4 -w 0000:05:10.0 -w 0000:05:10.1 -- -p 0x3 --config '(0,0,18),(1,0,19)' --parse-ptype
The number of rx_q equal to 1 and there is no problem. But, in l3fwd, the number of tx_q would equal to the number of core used in l3fwd, so here number of tx_q equal to 2 but as described above, the max number of queue can be used in VF is just only 1. So there is problem and l3fwd will check failed.
So there is two ways to fix this bug, the first is using this patch, don't assign RTE_ETH_DEV_SRIOV(dev).nb_q_per_pool as 1 when mq_mode = ETH_MQ_RX_VMDQ_ONLY.
And the second is that the number of tx_q would not assigned as the number of cores used in l3fwd.
Which one do you think is make sense?
Yanglong
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Wu, Yanglong
Sent: Thursday, January 11, 2018 6:30 PM
To: Dai, Wei <wei.dai@intel.com>; dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v4] net/ixgbe: fix l3fwd start failed on VF
Yes, this problem is caused by PF passing a wrong number of queue to VF. So basically, I removed model check of "case ETH_MQ_RX_NONE". It seem right after I do that but I'am also not very sure the changing is really right. So thank to your comments, I will redebug this problem.
-----Original Message-----
From: Dai, Wei
Sent: Thursday, January 11, 2018 5:48 PM
To: Wu, Yanglong <yanglong.wu@intel.com>; dev@dpdk.org; Yang, Zhiyong <zhiyong.yang@intel.com>
Cc: Wu, Yanglong <yanglong.wu@intel.com>
Subject: RE: [dpdk-dev] [PATCH v4] net/ixgbe: fix l3fwd start failed on VF
According to 82599 datasheet, VF working mode is controlled by its host PF.
If VF is working in RSS or DCB mode, it can use more than 1 queues.
That also means its host PF should enable RSS or DCB.
The PF Rx mode can be ETH_MQ_RX_VMDQ_RSS or ETH_MQ_RX_VMDQ_DCB.
So I think that DPDK app with PF cause this issue, not ixgbe PMD itself.
By the way, you can reply your patch mail to provide more info about how You reproduce this issue to easy others' reviewing and testing your patch.
Thanks
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Yanglong Wu
> Sent: Tuesday, January 9, 2018 2:32 PM
> To: dev@dpdk.org; Yang, Zhiyong <zhiyong.yang@intel.com>
> Cc: Wu, Yanglong <yanglong.wu@intel.com>
> Subject: [dpdk-dev] [PATCH v4] net/ixgbe: fix l3fwd start failed on VF
>
> VF can't run in multi queue mode, if nb_q_per_pool was set as 1.
> Nb_q_per_pool is passed through to max_rx_q and max_tx_q in VF.
> So if nb_q_per_pool is equal to 1, max_rx_q and max_tx_q can't be more
> than 1 and VF multi queue mode will fail.
>
> Fixes: 27b609cbd1c6 (ethdev: move the multi-queue mode check)
>
> Signed-off-by: Yanglong Wu <yanglong.wu@intel.com>
> ---
> v1~v3:
> coding style issue fix
> ---
> v4:
> Rework according to comments
> ---
> drivers/net/ixgbe/ixgbe_ethdev.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/net/ixgbe/ixgbe_ethdev.c
> b/drivers/net/ixgbe/ixgbe_ethdev.c
> index baaeee5d9..6af4f8b2b 100644
> --- a/drivers/net/ixgbe/ixgbe_ethdev.c
> +++ b/drivers/net/ixgbe/ixgbe_ethdev.c
> @@ -2240,8 +2240,6 @@ ixgbe_check_mq_mode(struct rte_eth_dev *dev)
> case ETH_MQ_RX_NONE:
> /* if nothing mq mode configure, use default scheme */
> dev->data->dev_conf.rxmode.mq_mode = ETH_MQ_RX_VMDQ_ONLY;
> - if (RTE_ETH_DEV_SRIOV(dev).nb_q_per_pool > 1)
> - RTE_ETH_DEV_SRIOV(dev).nb_q_per_pool = 1;
> break;
> default: /* ETH_MQ_RX_DCB, ETH_MQ_RX_DCB_RSS or ETH_MQ_TX_DCB*/
> /* SRIOV only works in VMDq enable mode */
> --
> 2.11.0
next prev parent reply other threads:[~2018-01-11 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171102161031.167892-1-yanglong.wu@intel.com>
2017-11-20 2:00 ` [dpdk-dev] [PATCH v2] " Yanglong Wu
2017-11-20 2:25 ` [dpdk-dev] [PATCH v3] " Yanglong Wu
2017-11-20 2:37 ` Yang, Zhiyong
2018-01-09 6:32 ` [dpdk-dev] [PATCH v4] " Yanglong Wu
2018-01-11 9:48 ` Dai, Wei
2018-01-11 10:29 ` Wu, Yanglong
2018-01-11 15:29 ` Wu, Yanglong [this message]
2018-01-12 2:38 ` Wu, Yanglong
2018-01-12 3:03 ` Dai, Wei
2018-01-13 3:30 ` Zhang, Helin
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=B73B41DFFD120A45AEE57672FCA463BA0195C845@shsmsx102.ccr.corp.intel.com \
--to=yanglong.wu@intel.com \
--cc=dev@dpdk.org \
--cc=wei.dai@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).