DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Radu Nicolau <radu.nicolau@intel.com>
Cc: hemant.agrawal@nxp.com, gakhil@marvell.com, anoobj@marvell.com,
	declan.doherty@intel.com, abhijit.sinha@intel.com,
	daniel.m.buckley@intel.com, marchana@marvell.com,
	ktejasree@marvell.com, matan@nvidia.com,
	konstantin.ananyev@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 2/2] doc: announce rte_security_ipsec_xform structure changes
Date: Sun, 08 Aug 2021 17:10:53 +0200	[thread overview]
Message-ID: <2570786.lMGgrh6d1K@thomas> (raw)
In-Reply-To: <20210805102055.308899-2-radu.nicolau@intel.com>

05/08/2021 12:20, Radu Nicolau:
> Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>
> ---
> +  * security: The structure ``rte_security_ipsec_xform`` will be extended with 
> +  multiple fields: udp structure that will hold the source and destination port 
> +  for UDP encapsulation, mss to specify the IPsec payload Maximum Segment Size, 
> +  esn structure for Extended Sequence Number.

Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
Acked-by: Anoob Joseph <anoobj@marvell.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>

Slightly reworded and applied:

* security: The structure ``rte_security_ipsec_xform`` will be extended with
  multiple fields: source and destination port of UDP encapsulation,
  IPsec payload MSS (Maximum Segment Size), and ESN (Extended Sequence Number).




  parent reply	other threads:[~2021-08-08 15:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-05 10:20 [dpdk-dev] [PATCH 1/2] doc: announce ipsec rte_ipsec_sa_prm " Radu Nicolau
2021-08-05 10:20 ` [dpdk-dev] [PATCH 2/2] doc: announce rte_security_ipsec_xform " Radu Nicolau
2021-08-05 10:42   ` Ananyev, Konstantin
2021-08-05 11:33   ` [dpdk-dev] [EXT] " Anoob Joseph
2021-08-08 12:17   ` [dpdk-dev] " Slava Ovsiienko
2021-08-08 15:10   ` Thomas Monjalon [this message]
2021-08-05 10:40 ` [dpdk-dev] [PATCH 1/2] doc: announce ipsec rte_ipsec_sa_prm " Ananyev, Konstantin
2021-08-07 13:35   ` Jerin Jacob
2021-08-08 12:18 ` Slava Ovsiienko
2021-08-08 15:04   ` Thomas Monjalon

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=2570786.lMGgrh6d1K@thomas \
    --to=thomas@monjalon.net \
    --cc=abhijit.sinha@intel.com \
    --cc=anoobj@marvell.com \
    --cc=daniel.m.buckley@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=ktejasree@marvell.com \
    --cc=marchana@marvell.com \
    --cc=matan@nvidia.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 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).