From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: Radu Nicolau <radu.nicolau@intel.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"gakhil@marvell.com" <gakhil@marvell.com>,
"anoobj@marvell.com" <anoobj@marvell.com>,
"declan.doherty@intel.com" <declan.doherty@intel.com>,
"abhijit.sinha@intel.com" <abhijit.sinha@intel.com>,
"daniel.m.buckley@intel.com" <daniel.m.buckley@intel.com>,
"marchana@marvell.com" <marchana@marvell.com>,
"ktejasree@marvell.com" <ktejasree@marvell.com>,
Matan Azrad <matan@nvidia.com>,
"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 2/2] doc: announce rte_security_ipsec_xform structure changes
Date: Sun, 8 Aug 2021 12:17:41 +0000 [thread overview]
Message-ID: <DM6PR12MB37538EE9774648407F7BC5CBDFF59@DM6PR12MB3753.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210805102055.308899-2-radu.nicolau@intel.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Radu Nicolau
> Sent: Thursday, August 5, 2021 13:21
> To: 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 Azrad <matan@nvidia.com>;
> konstantin.ananyev@intel.com
> Cc: dev@dpdk.org; Radu Nicolau <radu.nicolau@intel.com>
> Subject: [dpdk-dev] [PATCH 2/2] doc: announce rte_security_ipsec_xform
> structure changes
>
> Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>
> ---
> doc/guides/rel_notes/deprecation.rst | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst
> b/doc/guides/rel_notes/deprecation.rst
> index b87fa54e67..a3493b4dfb 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -196,3 +196,8 @@ Deprecation Notices
>
> * ipsec: The structure ``rte_ipsec_sa_prm`` will be extended with a new
> field ``hdr_l3_len`` to configure tunnel l3 header lenght.
> +
> + * 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.
> --
> 2.25.1
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
next prev parent reply other threads:[~2021-08-08 12:17 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 ` Slava Ovsiienko [this message]
2021-08-08 15:10 ` [dpdk-dev] " Thomas Monjalon
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=DM6PR12MB37538EE9774648407F7BC5CBDFF59@DM6PR12MB3753.namprd12.prod.outlook.com \
--to=viacheslavo@nvidia.com \
--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).