From: Archana Muniganti <marchana@marvell.com>
To: <gakhil@marvell.com>, <roy.fan.zhang@intel.com>,
<hemant.agrawal@nxp.com>, <konstantin.ananyev@intel.com>
Cc: Archana Muniganti <marchana@marvell.com>, <anoobj@marvell.com>,
<jerinj@marvell.com>, <dev@dpdk.org>
Subject: [dpdk-dev] [PATCH] doc: announce SA config option struct changes
Date: Wed, 30 Jun 2021 16:50:49 +0530 [thread overview]
Message-ID: <20210630112049.3747-1-marchana@marvell.com> (raw)
Proposing following two new fields for IPsec inner checksum
configuration in the structure ``rte_security_ipsec_sa_options``.
uint32_t ip_csum_enable : 1;
uint32_t l4_csum_enable : 1;
With these config options, per SA, application can specify if
the inner checksum(compute/verify) to be offloaded to the
security device.
https://mails.dpdk.org/archives/dev/2021-June/212977.html
Signed-off-by: Archana Muniganti <marchana@marvell.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 9584d6bfd7..da65ae68be 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -141,6 +141,10 @@ Deprecation Notices
in "rte_sched.h". These changes are aligned to improvements suggested in the
RFC https://mails.dpdk.org/archives/dev/2018-November/120035.html.
+* security: The IPsec SA config options structure ``struct rte_security_ipsec_sa_options``
+ will be updated with two new fields to support IPsec inner checksum in case
+ of protocol offload.
+
* metrics: The function ``rte_metrics_init`` will have a non-void return
in order to notify errors instead of calling ``rte_exit``.
--
2.22.0
next reply other threads:[~2021-06-30 11:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 11:20 Archana Muniganti [this message]
2021-07-31 17:53 ` Akhil Goyal
2021-07-31 17:44 Akhil Goyal
2021-08-02 9:43 ` Anoob Joseph
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
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=20210630112049.3747-1-marchana@marvell.com \
--to=marchana@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=konstantin.ananyev@intel.com \
--cc=roy.fan.zhang@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).