DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Marcin Smoczynski <marcinx.smoczynski@intel.com>,
	"marko.kovacevic@intel.com" <marko.kovacevic@intel.com>,
	"orika@mellanox.com" <orika@mellanox.com>,
	"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
	"pablo.de.lara.guarch@intel.com" <pablo.de.lara.guarch@intel.com>,
	"radu.nicolau@intel.com" <radu.nicolau@intel.com>,
	"tomasz.kantecki@intel.com" <tomasz.kantecki@intel.com>,
	"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>,
	"bernard.iremonger@intel.com" <bernard.iremonger@intel.com>,
	"olivier.matz@6wind.com" <olivier.matz@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 0/4] IPv6 with options support for IPsec transport
Date: Tue, 25 Jun 2019 12:59:13 +0000	[thread overview]
Message-ID: <VE1PR04MB66398C6AF411556B8CFC27EBE6E30@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20190624134000.2456-1-marcinx.smoczynski@intel.com>



> 
> Add support for IPv6 with header extensions (IPv6 options) and IPsec
> transport mode:
> 1. Add IPv6 header extension parsing method in librte_net
> 2. Fix IPv6 header with extension parsing in both librte_ipsec and
>    ipsec sample application using abovementioned function
> 3. Add new testing mechanism for ipsec-secgw sample application which
>    allows to automatically check how custom packets are processed.
> 
> This patchset depends on the following patch:
> http://patchwork.dpdk.org/patch/53406/
> 
> Marcin Smoczynski (4):
>   net: new ipv6 header extension parsing function
>   ipsec: fix transport mode for ipv6 with extensions
>   examples/ipsec-secgw: add support for ipv6 options
>   examples/ipsec-secgw: add scapy based unittests
> 
>  examples/ipsec-secgw/ipsec-secgw.c            |  35 +++-
>  examples/ipsec-secgw/sa.c                     |   5 +-
>  examples/ipsec-secgw/test/common_defs.sh      |  58 +-----
>  .../ipsec-secgw/test/common_defs_secgw.sh     |  65 +++++++
>  examples/ipsec-secgw/test/pkttest.py          | 127 ++++++++++++
>  examples/ipsec-secgw/test/pkttest.sh          |  65 +++++++
>  examples/ipsec-secgw/test/run_test.sh         | 108 ++++++++---
>  examples/ipsec-secgw/test/trs_ipv6opts.py     | 181 ++++++++++++++++++
>  lib/Makefile                                  |   3 +-
>  lib/librte_ipsec/iph.h                        |  55 +++++-
>  lib/librte_net/rte_ip.h                       |  49 +++++
>  lib/meson.build                               |   2 +-
>  12 files changed, 649 insertions(+), 104 deletions(-)
>  create mode 100644 examples/ipsec-secgw/test/common_defs_secgw.sh
>  create mode 100755 examples/ipsec-secgw/test/pkttest.py
>  create mode 100755 examples/ipsec-secgw/test/pkttest.sh
>  mode change 100644 => 100755 examples/ipsec-secgw/test/run_test.sh
>  create mode 100755 examples/ipsec-secgw/test/trs_ipv6opts.py
> 
> --
> 2.17.1

Series Acked-by: Akhil Goyal <akhil.goyal@nxp.com>

The dependent patch will go in mainline and is a generic patch to fix the compilation. So not holding this series.
Series Applied to dpdk-next-crypto

Thanks.

      parent reply	other threads:[~2019-06-25 12:59 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-08 10:47 [dpdk-dev] [PATCH 1/3] net: new ipv6 header extension parsing function Marcin Smoczynski
2019-05-08 10:47 ` Marcin Smoczynski
2019-05-08 10:47 ` [dpdk-dev] [PATCH 2/3] ipsec: fix transport mode for ipv6 with extensions Marcin Smoczynski
2019-05-08 10:47   ` Marcin Smoczynski
2019-05-14 12:42   ` Ananyev, Konstantin
2019-05-14 12:42     ` Ananyev, Konstantin
2019-06-20 12:07   ` Akhil Goyal
2019-05-08 10:47 ` [dpdk-dev] [PATCH 3/3] examples/ipsec-secgw: add support for ipv6 options Marcin Smoczynski
2019-05-08 10:47   ` Marcin Smoczynski
2019-05-14 12:51   ` Ananyev, Konstantin
2019-05-14 12:51     ` Ananyev, Konstantin
2019-05-14 12:48 ` [dpdk-dev] [PATCH 1/3] net: new ipv6 header extension parsing function Ananyev, Konstantin
2019-05-14 12:48   ` Ananyev, Konstantin
2019-06-20 11:40 ` Akhil Goyal
2019-06-20 17:40   ` Ananyev, Konstantin
2019-06-21  8:01     ` Akhil Goyal
2019-06-24 11:45       ` Smoczynski, MarcinX
2019-06-25 12:57         ` Akhil Goyal
2019-06-24 13:39 ` [dpdk-dev] [PATCH v2 0/4] IPv6 with options support for IPsec transport Marcin Smoczynski
2019-06-24 13:39   ` [dpdk-dev] [PATCH v2 1/4] net: new ipv6 header extension parsing function Marcin Smoczynski
2019-06-24 18:54     ` Ananyev, Konstantin
2019-07-02  9:06     ` Olivier Matz
2019-06-24 13:39   ` [dpdk-dev] [PATCH v2 2/4] ipsec: fix transport mode for ipv6 with extensions Marcin Smoczynski
2019-06-24 18:55     ` Ananyev, Konstantin
2019-06-24 13:39   ` [dpdk-dev] [PATCH v2 3/4] examples/ipsec-secgw: add support for ipv6 options Marcin Smoczynski
2019-06-24 18:55     ` Ananyev, Konstantin
2019-06-24 13:40   ` [dpdk-dev] [PATCH v2 4/4] examples/ipsec-secgw: add scapy based unittests Marcin Smoczynski
2019-06-24 18:56     ` Ananyev, Konstantin
2019-06-25 12:59   ` Akhil Goyal [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=VE1PR04MB66398C6AF411556B8CFC27EBE6E30@VE1PR04MB6639.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=bernard.iremonger@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=marcinx.smoczynski@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=olivier.matz@6wind.com \
    --cc=orika@mellanox.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=radu.nicolau@intel.com \
    --cc=tomasz.kantecki@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).