From: "Yang, Zhiyong" <zhiyong.yang@intel.com>
To: "Wu, Yanglong" <yanglong.wu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Wu, Yanglong" <yanglong.wu@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] net/ixgbe: fix l3fwd start failed on VF
Date: Mon, 20 Nov 2017 02:37:54 +0000 [thread overview]
Message-ID: <E182254E98A5DA4EB1E657AC7CB9BD2A8B008362@BGSMSX101.gar.corp.intel.com> (raw)
In-Reply-To: <20171120022557.151461-1-yanglong.wu@intel.com>
Hi Yanglong,
You should write something after SoB, which makes reviewer easier to know
What changes are since last version.
Thanks
Zhiyong
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Yanglong Wu
> Sent: Monday, November 20, 2017 10:26 AM
> To: dev@dpdk.org
> Cc: Wu, Yanglong <yanglong.wu@intel.com>
> Subject: [dpdk-dev] [PATCH v3] 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>
> ---
Changes in V3:
next prev parent reply other threads:[~2017-11-20 2:38 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 [this message]
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
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=E182254E98A5DA4EB1E657AC7CB9BD2A8B008362@BGSMSX101.gar.corp.intel.com \
--to=zhiyong.yang@intel.com \
--cc=dev@dpdk.org \
--cc=yanglong.wu@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).