DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Sun, QinX" <qinx.sun@intel.com>
To: "Rong, Leyi" <leyi.rong@intel.com>,
	"Zhang, Qi Z" <qi.z.zhang@intel.com>,
	 "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Rong, Leyi" <leyi.rong@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/iavf: fix VLAN tag extraction handling in AVX512 path
Date: Thu, 29 Apr 2021 06:45:01 +0000	[thread overview]
Message-ID: <SJ0PR11MB48634028666E14E55C908181875F9@SJ0PR11MB4863.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210422024830.10617-1-leyi.rong@intel.com>

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Leyi Rong
> Sent: Thursday, April 22, 2021 10:49 AM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>; Lu, Wenzhuo
> <wenzhuo.lu@intel.com>
> Cc: dev@dpdk.org; Rong, Leyi <leyi.rong@intel.com>
> Subject: [dpdk-dev] [PATCH] net/iavf: fix VLAN tag extraction handling in
> AVX512 path
> 
> The new VIRTCHNL_VF_OFFLOAD_VLAN_V2 capability added support that
> allows the PF to set the location of the RX VLAN tag for stripping offloads.
> 
> So the VF needs to extract the VLAN tag according to the location flags.
> 
> This patch is the fix for AVX512 path, as AVX2 is already fixed.
> 
> Fixes: 9c9aa0040344 ("net/iavf: add offload path for Rx AVX512 flex
> descriptor")
> 
> Signed-off-by: Leyi Rong <leyi.rong@intel.com>

Tested-by: Qin Sun  <qinx.sun@intel.com>

  parent reply	other threads:[~2021-04-29  6:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22  2:48 Leyi Rong
2021-04-27  7:11 ` Sun, QinX
2021-04-28  1:58   ` Zhang, Qi Z
2021-04-29  6:45 ` Sun, QinX [this message]
2021-04-30 14:07   ` Zhang, Qi Z

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=SJ0PR11MB48634028666E14E55C908181875F9@SJ0PR11MB4863.namprd11.prod.outlook.com \
    --to=qinx.sun@intel.com \
    --cc=dev@dpdk.org \
    --cc=leyi.rong@intel.com \
    --cc=qi.z.zhang@intel.com \
    --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).