From: Akhil Goyal <gakhil@marvell.com>
To: Archana Muniganti <marchana@marvell.com>,
"roy.fan.zhang@intel.com" <roy.fan.zhang@intel.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>
Cc: Archana Muniganti <marchana@marvell.com>,
Anoob Joseph <anoobj@marvell.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: announce SA config option struct changes
Date: Sat, 31 Jul 2021 17:53:43 +0000 [thread overview]
Message-ID: <CO6PR18MB4484ED83F00A362F1669BB92D8ED9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20210630112049.3747-1-marchana@marvell.com>
> 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>
> ---
Marking this patch as Not applicable,
As a new patch is submitted for consolidating all notices for same structure.
https://mails.dpdk.org/archives/dev/2021-July/215906.html
next prev parent reply other threads:[~2021-07-31 17:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 11:20 Archana Muniganti
2021-07-31 17:53 ` Akhil Goyal [this message]
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=CO6PR18MB4484ED83F00A362F1669BB92D8ED9@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=konstantin.ananyev@intel.com \
--cc=marchana@marvell.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).