From: Thomas Monjalon <thomas@monjalon.net>
To: "Zhang, Qi Z" <qi.z.zhang@intel.com>
Cc: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
mschmidt <mschmidt@redhat.com>, "dev@dpdk.org" <dev@dpdk.org>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"Rong, Leyi" <leyi.rong@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>,
helin.zhang@intel.com, david.marchand@redhat.com
Subject: Re: [PATCH] net/iavf: fix VLAN offload with AVX512
Date: Mon, 12 Jun 2023 20:02:02 +0200 [thread overview]
Message-ID: <4584961.CvnuH1ECHv@thomas> (raw)
In-Reply-To: <DM4PR11MB5994586DE5A6E65374DD9630D7929@DM4PR11MB5994.namprd11.prod.outlook.com>
03/04/2023 07:39, Zhang, Qi Z:
> > > 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.
> > >
> > > This fix is for the AVX512 Rx path. The same bug in AVX2 was fixed by
> > > commit
> > > eb24917428a1 ("net/iavf: fix VLAN offload with AVX2").
> > >
> > > Fixes: 4b64ccb328c9 ("net/iavf: fix VLAN extraction in AVX512 path")
> > > Cc: stable@dpdk.org
> > >
> > > Signed-off-by: Michal Schmidt <mschmidt@redhat.com>
> > Acked-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
>
> Applied to dpdk-next-net-intel.
I don't find this patch in your tree.
Is it lost somewhere?
next prev parent reply other threads:[~2023-06-12 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 10:07 Michal Schmidt
2023-03-29 1:05 ` Lu, Wenzhuo
2023-04-03 5:39 ` Zhang, Qi Z
2023-06-12 18:02 ` Thomas Monjalon [this message]
2023-06-13 0:38 ` 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=4584961.CvnuH1ECHv@thomas \
--to=thomas@monjalon.net \
--cc=beilei.xing@intel.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=jingjing.wu@intel.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=leyi.rong@intel.com \
--cc=mschmidt@redhat.com \
--cc=qi.z.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).