DPDK patches and discussions
 help / color / mirror / Atom feed
From: Anoob Joseph <anoobj@marvell.com>
To: Akhil Goyal <gakhil@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "radu.nicolau@intel.com" <radu.nicolau@intel.com>,
	"declan.doherty@intel.com" <declan.doherty@intel.com>,
	"abhijits.sinha@intel.com" <abhijits.sinha@intel.com>,
	"daniel.m.buckley@intel.com" <daniel.m.buckley@intel.com>,
	Archana Muniganti <marchana@marvell.com>,
	Tejasree Kondoj <ktejasree@marvell.com>,
	"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
	"matan@nvidia.com" <matan@nvidia.com>,
	"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>,
	Akhil Goyal <gakhil@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce SA config option struct changes
Date: Mon, 2 Aug 2021 09:43:19 +0000	[thread overview]
Message-ID: <PH0PR18MB46720DF67DA3722EE4F3FF24DFEF9@PH0PR18MB4672.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20210731174428.626705-1-gakhil@marvell.com>

Hi Akhil,

There are 2 more items that I would like to add.
- IV gen (in ``rte_security_ipsec_sa_options``)
- SA lifetime configuration (in ``rte_security_ipsec_xform``)

http://patches.dpdk.org/project/dpdk/patch/1626759974-334-2-git-send-email-anoobj@marvell.com/
http://patches.dpdk.org/project/dpdk/patch/1626759974-334-3-git-send-email-anoobj@marvell.com/

Do you recommend sending separate deprecation notice or can this patch be updated to cover those as well?

Thanks,
Anoob

> -----Original Message-----
> From: Akhil Goyal <gakhil@marvell.com>
> Sent: Saturday, July 31, 2021 11:14 PM
> To: dev@dpdk.org
> Cc: Anoob Joseph <anoobj@marvell.com>; radu.nicolau@intel.com;
> declan.doherty@intel.com; abhijits.sinha@intel.com;
> daniel.m.buckley@intel.com; Archana Muniganti <marchana@marvell.com>;
> Tejasree Kondoj <ktejasree@marvell.com>; hemant.agrawal@nxp.com;
> matan@nvidia.com; konstantin.ananyev@intel.com; Akhil Goyal
> <gakhil@marvell.com>
> Subject: [PATCH] doc: announce SA config option struct changes
> 
> From: Archana Muniganti <marchana@marvell.com>
> 
> Propose new fields to support offloads like
> - IPsec inner checksum(L3/L4)
> - IPsec tunnel header verification
> - TSO
> - etc
> in the structure ``rte_security_ipsec_sa_options``.
> 
> Signed-off-by: Archana Muniganti <marchana@marvell.com>
> Signed-off-by: Tejasree Kondoj <ktejasree@marvell.com>
> Acked-by: Akhil Goyal <gakhil@marvell.com>
> ---
> Proposal for changes are floated as per below links.
> https://mails.dpdk.org/archives/dev/2021-June/212977.html
> https://mails.dpdk.org/archives/dev/2021-July/213484.html
> https://mails.dpdk.org/archives/dev/2021-July/214521.html
> 
> Cc: Radu Nicolau <radu.nicolau@intel.com>
> 
>  doc/guides/rel_notes/deprecation.rst | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/doc/guides/rel_notes/deprecation.rst
> b/doc/guides/rel_notes/deprecation.rst
> index 6a35c7649a..96192b4a41 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -151,3 +151,7 @@ Deprecation Notices
>  * security: The functions ``rte_security_set_pkt_metadata`` and
>    ``rte_security_get_userdata`` will be made inline functions and additional
>    flags will be added in structure ``rte_security_ctx`` in DPDK 21.11.
> +
> +* security: The IPsec SA config options ``struct
> rte_security_ipsec_sa_options``
> +  will be updated with new fields to support new features like IPsec inner
> +  checksum, tunnel header verification, TSO in case of protocol offload.
> --
> 2.25.1


  reply	other threads:[~2021-08-02  9:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-31 17:44 Akhil Goyal
2021-08-02  9:43 ` Anoob Joseph [this message]
2021-08-02 12:41   ` Akhil Goyal
2021-08-04 17:03 ` Akhil Goyal
2021-08-05 10:00 ` Nicolau, Radu
2021-08-05 10:14   ` Hemant Agrawal
2021-08-07 13:31     ` Jerin Jacob
2021-08-07 17:17   ` Thomas Monjalon
  -- strict thread matches above, loose matches on Subject: below --
2021-06-30 11:20 Archana Muniganti
2021-07-31 17:53 ` Akhil Goyal

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=PH0PR18MB46720DF67DA3722EE4F3FF24DFEF9@PH0PR18MB4672.namprd18.prod.outlook.com \
    --to=anoobj@marvell.com \
    --cc=abhijits.sinha@intel.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).