All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Tejasree Kondoj <ktejasree@marvell.com>,
	Radu Nicolau <radu.nicolau@intel.com>
Cc: Narayana Prasad <pathreya@marvell.com>,
	Anoob Joseph <anoobj@marvell.com>,  "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] security: allow application to specify UDP ports to PMD
Date: Thu, 10 Sep 2020 19:09:26 +0000	[thread overview]
Message-ID: <VI1PR04MB3168BACEB16188A6AC1FF6DDE6270@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20200903064206.16208-1-ktejasree@marvell.com>

Hi Tejasree,

> Add UDP source and destination ports in ipsec_xform to allow application
> to specify ports to be used for IPsec UDP encapsulation as they are
> dynamically changed by NAT in between. Also adding an extra flag to
> indicate whether PMD needs to perform encapsulation header verification
> in case of inbound. In case of inline IPsec implementation, verification
> of outer IP headers and UDP encapsulation headers need to be handled
> in the PMD. For lookaside IPsec, application can optionally offload
> this to the PMD.
> 
> Signed-off-by: Tejasree Kondoj <ktejasree@marvell.com>
> ---

I think we should add some usage of these newly added params 
- either in app/test or in examples/ipsec-secgw

Regards,
Akhil

  reply	other threads:[~2020-09-10 19:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-03  6:42 [dpdk-dev] [PATCH] security: allow application to specify UDP ports to PMD Tejasree Kondoj
2020-09-10 19:09 ` Akhil Goyal [this message]
2020-09-21  9:13   ` Tejasree Kondoj
2020-09-21  9:30     ` Akhil Goyal
2020-09-21 12:03       ` Tejasree Kondoj
2021-01-11 19:20         ` Akhil Goyal
2021-01-12  6:51           ` Tejasree Kondoj

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=VI1PR04MB3168BACEB16188A6AC1FF6DDE6270@VI1PR04MB3168.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=ktejasree@marvell.com \
    --cc=pathreya@marvell.com \
    --cc=radu.nicolau@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.