DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Su, Simei" <simei.su@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Cao, Yahui" <yahui.cao@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/ice: fix FDIR when SPI as input set for ESP flow
Date: Tue, 13 Jul 2021 02:59:32 +0000	[thread overview]
Message-ID: <f316aec734f74c099a56bdb348cce0ac@intel.com> (raw)
In-Reply-To: <20210713021024.117748-1-simei.su@intel.com>



> -----Original Message-----
> From: Su, Simei <simei.su@intel.com>
> Sent: Tuesday, July 13, 2021 10:10 AM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>
> Cc: dev@dpdk.org; Cao, Yahui <yahui.cao@intel.com>; Su, Simei
> <simei.su@intel.com>
> Subject: [PATCH v2] net/ice: fix FDIR when SPI as input set for ESP flow
> 
> FDIR can't work when SPI as inputset for both ESP over IP and ESP over UDP
> flow. This patch fixes this issue by adding the corresponding input set for ESP
> over IP and ESP over UDP when parsing input set. Also, it adds input set bit for
> NAT_T_ESP to distinguish ESP over IP and ESP over UDP.
> 
> Fixes: 70feafc1a3f2 ("net/ice: support ESP/NATT flow director to match outer
> IP")
> 
> Signed-off-by: Simei Su <simei.su@intel.com>
> 
> v2:
> * Refine title and commit log to be more accurate.
> * Correct spelling mistakes in commit log.

Change log is not part of the commit log, should below "---"

Acked-by: Qi Zhang <qi.z.zhang@intel.com>

Applied to dpdk-next-net-intel.

Thanks
Qi


      reply	other threads:[~2021-07-13  2:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-12  9:39 [dpdk-dev] [PATCH] net/ice: fix SPI for ESP and NATT not work issue Simei Su
2021-07-13  1:07 ` Zhang, Qi Z
2021-07-13  1:44   ` Su, Simei
2021-07-13  2:10 ` [dpdk-dev] [PATCH v2] net/ice: fix FDIR when SPI as input set for ESP flow Simei Su
2021-07-13  2:59   ` Zhang, Qi Z [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=f316aec734f74c099a56bdb348cce0ac@intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=simei.su@intel.com \
    --cc=yahui.cao@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).