DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: "Zhang, Qi Z" <qi.z.zhang@intel.com>,
	"Jiale, SongX" <songx.jiale@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH] net/iavf: fix SCTP tunnel packet forwarding issue
Date: Thu, 6 Jul 2023 01:26:36 +0000	[thread overview]
Message-ID: <SN7PR11MB749135719FAB318E162258CD8C2CA@SN7PR11MB7491.namprd11.prod.outlook.com> (raw)
In-Reply-To: <DM4PR11MB5994BEC06F5C43F193C66FF4D725A@DM4PR11MB5994.namprd11.prod.outlook.com>

Hi Qi,

> -----Original Message-----
> From: Zhang, Qi Z <qi.z.zhang@intel.com>
> Sent: Thursday, June 29, 2023 4:58 PM
> To: Jiale, SongX <songx.jiale@intel.com>; Lu, Wenzhuo
> <wenzhuo.lu@intel.com>; dev@dpdk.org
> Cc: Lu, Wenzhuo <wenzhuo.lu@intel.com>
> Subject: RE: [PATCH] net/iavf: fix SCTP tunnel packet forwarding issue
> 
> 
> 
> > -----Original Message-----
> > From: Jiale, SongX <songx.jiale@intel.com>
> > Sent: Wednesday, June 28, 2023 3:33 PM
> > To: Lu, Wenzhuo <wenzhuo.lu@intel.com>; dev@dpdk.org
> > Cc: Lu, Wenzhuo <wenzhuo.lu@intel.com>
> > Subject: RE: [PATCH] net/iavf: fix SCTP tunnel packet forwarding issue
> >
> > > -----Original Message-----
> > > From: Wenzhuo Lu <wenzhuo.lu@intel.com>
> > > Sent: Wednesday, June 21, 2023 9:15 AM
> > > To: dev@dpdk.org
> > > Cc: Lu, Wenzhuo <wenzhuo.lu@intel.com>
> > > Subject: [PATCH] net/iavf: fix SCTP tunnel packet forwarding issue
> > >
> > > The SCTP tunnel packets cannot be forwarded in AVX2 mode.
> > >
> > > As 2 features are developed in parallel, 5712bf9d6e14
> > > ("net/iavf: add Tx AVX2 offload path") doesn't consider the impact
> > > of 4f8259df563a ("net/iavf: enable Tx outer checksum offload on
> AVX512").
> > > So, the wrong TX path is selected.
> > >
> > > Fixes: 5712bf9d6e14 ("net/iavf: add Tx AVX2 offload path")
> > >
> > > Signed-off-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
> > > ---
> > Tested-by: Song Jiale <songx.jiale@intel.com>
> 
> Applied to dpdk-next-net-intel.
> 
> Thanks
> Qi
Sorry, this fix is not good because of some misunderstanding. Would you like helping to revert it? We'll send a new one to fix the issue. Thanks.

  reply	other threads:[~2023-07-06  1:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-21  1:15 Wenzhuo Lu
2023-06-28  7:32 ` Jiale, SongX
2023-06-29  8:57   ` Zhang, Qi Z
2023-07-06  1:26     ` Lu, Wenzhuo [this message]
2023-07-06  1:32       ` 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=SN7PR11MB749135719FAB318E162258CD8C2CA@SN7PR11MB7491.namprd11.prod.outlook.com \
    --to=wenzhuo.lu@intel.com \
    --cc=dev@dpdk.org \
    --cc=qi.z.zhang@intel.com \
    --cc=songx.jiale@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).