From: "Nicolau, Radu" <radu.nicolau@intel.com>
To: Akhil Goyal <gakhil@marvell.com>, <dev@dpdk.org>
Cc: <anoobj@marvell.com>, <declan.doherty@intel.com>,
<abhijits.sinha@intel.com>, <daniel.m.buckley@intel.com>,
<marchana@marvell.com>, <ktejasree@marvell.com>,
<hemant.agrawal@nxp.com>, <matan@nvidia.com>,
<konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce SA config option struct changes
Date: Thu, 5 Aug 2021 11:00:25 +0100 [thread overview]
Message-ID: <db5db13c-8de4-d23f-e40e-f27572c38821@intel.com> (raw)
In-Reply-To: <20210731174428.626705-1-gakhil@marvell.com>
On 7/31/2021 6:44 PM, Akhil Goyal wrote:
> 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>
Acked-by: Radu Nicolau <radu.nicolau@intel.com>
next prev parent reply other threads:[~2021-08-05 10:00 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
2021-08-02 12:41 ` Akhil Goyal
2021-08-04 17:03 ` Akhil Goyal
2021-08-05 10:00 ` Nicolau, Radu [this message]
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=db5db13c-8de4-d23f-e40e-f27572c38821@intel.com \
--to=radu.nicolau@intel.com \
--cc=abhijits.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 \
/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).