From: "Zhang, Helin" <helin.zhang@intel.com>
To: "Dai, Wei" <wei.dai@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Wu, Yanglong" <yanglong.wu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Dai, Wei" <wei.dai@intel.com>,
Wei Dai <weid.dai@intel.com>
Subject: Re: [dpdk-dev] [PATCH v5] net/ixgbe: fix to config VLAN strip on the fly
Date: Mon, 21 May 2018 01:15:51 +0000 [thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E71AED04AA@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1526724679-54877-1-git-send-email-wei.dai@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Wei Dai
> Sent: Saturday, May 19, 2018 6:11 PM
> To: Zhang, Qi Z; Yigit, Ferruh; Lu, Wenzhuo; Ananyev, Konstantin; Wu,
> Yanglong
> Cc: dev@dpdk.org; Dai, Wei; stable@dpdk.org; Wei Dai
> Subject: [dpdk-dev] [PATCH v5] net/ixgbe: fix to config VLAN strip on the fly
>
> The old ixgbe_vlan_offload_set() is called by
> rte_eth_dev_set_vlan_offload() which is meant to config VLAN
> strip/filter/extend on all queues.
> This old function is also called by rte_eth_dev_start()/ixgbe_dev_start()
> which need support per-queue VALN strip on only parts of queues.
>
> So add new function ixgbe_vlan_offload_config() = old
> ixgbe_vlan_offload_set().
> This new function is called by ixgbe_dev_start() to support VLAN strip per-
> queue configuration.
>
> New ixgbe_vlan_offload_set() = codes to align VLAN strip flags on all queues
> with port level setting + new ixgbe_vlan_offload_configure().
> The 2nd function is called by rte_eth_dev_set_vlan_offload to support
> configure VLAN strip on all queues of whole port.
>
> Fixes: 216f78f4d53f ("net/ixgbe: support VLAN strip per queue offloading in PF")
> Fixes: 860a94d3c692 ("net/ixgbe: support VLAN strip per queue offloading in
> VF")
>
> Cc: stable@dpdk.org
>
> Signed-off-by: Wei Dai <weid.dai@intel.com>
> Signed-off-by: Yanglong Wu <yanglong.wu@intel.com>
>
> Acked-by: Qi Zhang <qi.z.zhang@intel.com>
Applied to dpdk-next-net-intel, thanks!
/Helin
prev parent reply other threads:[~2018-05-21 1:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 5:52 [dpdk-dev] [PATCH] net/ixgbe: fix VLAN strip setting fail for per port Yanglong Wu
2018-05-17 15:49 ` Zhang, Qi Z
2018-05-18 7:16 ` [dpdk-dev] [DPDK] " Yanglong Wu
2018-05-18 7:23 ` [dpdk-dev] [PATCH v2] " Yanglong Wu
2018-05-18 7:45 ` Zhang, Qi Z
2018-05-18 11:06 ` Dai, Wei
2018-05-18 12:36 ` Zhang, Qi Z
2018-05-18 14:08 ` Ferruh Yigit
2018-05-18 15:05 ` Dai, Wei
2018-05-18 16:10 ` Dai, Wei
2018-05-18 15:43 ` [dpdk-dev] [PATCH v3] net/ixgbe: config VLAN strip on the fly Wei Dai
2018-05-18 16:08 ` [dpdk-dev] [PATCH v4] " Wei Dai
2018-05-19 0:19 ` Zhang, Qi Z
2018-05-19 10:32 ` Dai, Wei
2018-05-19 10:11 ` [dpdk-dev] [PATCH v5] net/ixgbe: fix to " Wei Dai
2018-05-21 1:15 ` Zhang, Helin [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=F35DEAC7BCE34641BA9FAC6BCA4A12E71AED04AA@SHSMSX103.ccr.corp.intel.com \
--to=helin.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=wei.dai@intel.com \
--cc=weid.dai@intel.com \
--cc=wenzhuo.lu@intel.com \
--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).