From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: mschmidt <mschmidt@redhat.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"Wang, Haiyue" <haiyue.wang@intel.com>
Subject: RE: [PATCH] net/iavf: fix mbuf VLAN offload flags in the L2TAG2 path with AVX2
Date: Wed, 14 Dec 2022 02:06:17 +0000 [thread overview]
Message-ID: <DM5PR11MB17871ACEA616D0B82D409B8C8CE09@DM5PR11MB1787.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221208121916.155132-1-mschmidt@redhat.com>
> -----Original Message-----
> From: Michal Schmidt <mschmidt@redhat.com>
> Sent: Thursday, December 8, 2022 8:19 PM
> To: dev@dpdk.org
> Cc: Richardson, Bruce <bruce.richardson@intel.com>; Wu, Jingjing
> <jingjing.wu@intel.com>; Xing, Beilei <beilei.xing@intel.com>; Wang, Haiyue
> <haiyue.wang@intel.com>
> Subject: [PATCH] net/iavf: fix mbuf VLAN offload flags in the L2TAG2 path with
> AVX2
>
> It has been observed that mbufs of some received VLAN packets had the VLAN
> tag correctly set in vlan_tci, but ol_flags were missing the VLAN-indicating
> flags.
>
> _mm256_shuffle_epi8 operates as two independent 128-bit operations, not as
> a single 256-bit operation. To have the RTE_MBUF_F_RX_VLAN* flags reflected
> in the resulting vlan_flags for all 8 rx descriptors, the input l2tag2_flags_shuf
> must contain the required pattern in both 128-bit halves.
>
> Fixes: 3a1aca384d3a ("net/iavf: fix VLAN tag extraction handling")
>
> Signed-off-by: Michal Schmidt <mschmidt@redhat.com>
Acked-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
next prev parent reply other threads:[~2022-12-14 2:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 12:19 Michal Schmidt
2022-12-13 8:17 ` Maxime Coquelin
2022-12-14 2:06 ` Lu, Wenzhuo [this message]
2023-02-14 1:48 ` 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=DM5PR11MB17871ACEA616D0B82D409B8C8CE09@DM5PR11MB1787.namprd11.prod.outlook.com \
--to=wenzhuo.lu@intel.com \
--cc=beilei.xing@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=haiyue.wang@intel.com \
--cc=jingjing.wu@intel.com \
--cc=mschmidt@redhat.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).