From: Bernard Iremonger <bernard.iremonger@intel.com>
To: dev@dpdk.org
Cc: beilei.xing@intel.com, wenzhuo.lu@intel.com, qi.zhang@intel.com,
Bernard Iremonger <bernard.iremonger@intel.com>,
stable@dpdk.org
Subject: [dpdk-stable] [PATCH v2] net/i40e: fix to ensure vector mode is not used
Date: Wed, 12 Apr 2017 16:28:34 +0100 [thread overview]
Message-ID: <1492010914-20274-1-git-send-email-bernard.iremonger@intel.com> (raw)
In-Reply-To: <1491922880-18702-1-git-send-email-bernard.iremonger@intel.com>
In rx vector mode, the QinQ VLAN tag is not stripped.
When hw_vlan_extend is set for QinQ ensure that
rx vector mode is not selected.
Fixes: 5b2d37858d32 ("net/i40e: fix single VLAN tag to be outer VLAN tag")
Cc: stable@dpdk.org
Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com>
---
Changes in v2:
Rebased to latest dpdk-next-net
Updated Fixes line.
Added Cc: line
drivers/net/i40e/i40e_rxtx_vec_common.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/net/i40e/i40e_rxtx_vec_common.h b/drivers/net/i40e/i40e_rxtx_vec_common.h
index 952fd4b63..692096684 100644
--- a/drivers/net/i40e/i40e_rxtx_vec_common.h
+++ b/drivers/net/i40e/i40e_rxtx_vec_common.h
@@ -234,6 +234,10 @@ i40e_rx_vec_dev_conf_condition_check_default(struct rte_eth_dev *dev)
if (rxmode->header_split == 1)
return -1;
+ /* no QinQ support */
+ if (rxmode->hw_vlan_extend == 1)
+ return -1;
+
return 0;
#else
RTE_SET_USED(dev);
--
2.11.0
next parent reply other threads:[~2017-04-12 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1491922880-18702-1-git-send-email-bernard.iremonger@intel.com>
2017-04-12 15:28 ` Bernard Iremonger [this message]
2017-04-13 9:53 ` [dpdk-stable] [PATCH v3] " Bernard Iremonger
2017-04-18 9:58 ` [dpdk-stable] [dpdk-dev] " Ananyev, Konstantin
2017-04-18 10:04 ` Ferruh Yigit
2017-04-19 13:10 ` Ferruh Yigit
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=1492010914-20274-1-git-send-email-bernard.iremonger@intel.com \
--to=bernard.iremonger@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=qi.zhang@intel.com \
--cc=stable@dpdk.org \
--cc=wenzhuo.lu@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).