DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Mariusz Drost <mariuszx.drost@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 0/2] fixes for inline-crypto ipsec
Date: Mon, 1 Jul 2019 11:39:00 +0000	[thread overview]
Message-ID: <VE1PR04MB6639C8794D88BE49FB102B37E6F90@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20190626132617.10576-1-mariuszx.drost@intel.com>


> 
> Fixes for ipsec-secgw application to work with inline crypto IPv4
> transport mode and IPv6 tunnel/transport modes.
> 
> v2:
> * Added comment to WITHOUT_TRANSPORT_VERSION macro
> * Added macros around all ipsec_sa flags checks
> 
> Mariusz Drost (2):
>   net/ixgbe: fix lack of ip type for crypto session
>   examples/ipsec-secgw: fix not working inline ipsec modes
> 
>  drivers/net/ixgbe/ixgbe_ipsec.c |   6 +-
>  examples/ipsec-secgw/esp.c      |  17 ++--
>  examples/ipsec-secgw/ipsec.c    |  21 +++--
>  examples/ipsec-secgw/ipsec.h    |  29 +++++-
>  examples/ipsec-secgw/sa.c       | 160 +++++++++++++++++++++++---------
>  examples/ipsec-secgw/sp4.c      |  24 ++++-
>  examples/ipsec-secgw/sp6.c      |  42 ++++++++-
>  7 files changed, 230 insertions(+), 69 deletions(-)
Patchset Applied to dpdk-next-crypto

Thanks.


      parent reply	other threads:[~2019-07-01 11:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <–20190604100644.13724-1-mariuszx.drost@intel.com>
2019-06-26 13:26 ` Mariusz Drost
2019-06-26 13:26   ` [dpdk-dev] [PATCH v2 1/2] net/ixgbe: fix lack of ip type for crypto session Mariusz Drost
2019-06-26 13:26   ` [dpdk-dev] [PATCH v2 2/2] examples/ipsec-secgw: fix not working inline ipsec modes Mariusz Drost
2019-07-01 11:38     ` Akhil Goyal
2019-07-01 11:39   ` 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=VE1PR04MB6639C8794D88BE49FB102B37E6F90@VE1PR04MB6639.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=mariuszx.drost@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).