From: Simei Su <simei.su@intel.com>
To: qi.z.zhang@intel.com
Cc: dev@dpdk.org, junfeng.guo@intel.com, yahui.cao@intel.com,
Simei Su <simei.su@intel.com>
Subject: [dpdk-dev] [PATCH v2 0/3] net/ice: support FDIR ESP and NATT to match outer IP
Date: Wed, 9 Jun 2021 10:49:48 +0800 [thread overview]
Message-ID: <20210609024951.382979-1-simei.su@intel.com> (raw)
In-Reply-To: <20210527055330.341052-1-simei.su@intel.com>
[PATCH v2 1/3] enable FDIR ESP to match outer IPV4/IPV6 SRC/DST field in DPDK AVF.
[PATCH v2 2/3] add IPV4/IPV6 SRC/DST input set for ESP/NAT_T_ESP in share code.
[PATCH v2 3/3] enable FDIR ESP/NAT_T_ESP match outer IPV4/IPV6 SRC/DST field in DPDK PF.
v2:
* Combine patch for "FDIR ESP support in DPDK AVF" with this patchset.
Simei Su (3):
net/iavf: add FDIR ESP support to match outer IP
net/ice/base: support FDIR ESP for outer IP match
net/ice: support FDIR ESP and NATT to match outer IP
drivers/net/iavf/iavf_fdir.c | 11 ++++--
drivers/net/ice/base/ice_fdir.c | 8 +++++
drivers/net/ice/ice_fdir_filter.c | 73 +++++++++++++++++++++++++++++++++++++++
3 files changed, 89 insertions(+), 3 deletions(-)
--
2.9.5
next prev parent reply other threads:[~2021-06-09 2:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 5:53 [dpdk-dev] [PATCH 0/2] " Simei Su
2021-05-27 5:53 ` [dpdk-dev] [PATCH 1/2] net/ice/base: support FDIR ESP for outer IP match Simei Su
2021-05-27 5:53 ` [dpdk-dev] [PATCH 2/2] net/ice: support FDIR ESP and NATT to match outer IP Simei Su
2021-06-09 2:49 ` Simei Su [this message]
2021-06-09 2:49 ` [dpdk-dev] [PATCH v2 1/3] net/iavf: add FDIR ESP support " Simei Su
2021-06-09 2:49 ` [dpdk-dev] [PATCH v2 2/3] net/ice/base: support FDIR ESP for outer IP match Simei Su
2021-06-09 2:49 ` [dpdk-dev] [PATCH v2 3/3] net/ice: support FDIR ESP and NATT to match outer IP Simei Su
2021-06-18 2:57 ` [dpdk-dev] [PATCH v2 0/3] " 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=20210609024951.382979-1-simei.su@intel.com \
--to=simei.su@intel.com \
--cc=dev@dpdk.org \
--cc=junfeng.guo@intel.com \
--cc=qi.z.zhang@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).