From: Radu Nicolau <radu.nicolau@intel.com>
To: Aakash Sasidharan <asasidharan@marvell.com>
Cc: <gakhil@marvell.com>, <jerinj@marvell.com>, <anoobj@marvell.com>,
<vvelumuri@marvell.com>, <dev@dpdk.org>,
<konstantin.v.ananyev@yandex.ru>, <vladimir.medvedkin@intel.com>
Subject: Re: [PATCH v3] doc: announce rte_ipsec API changes
Date: Tue, 30 Jul 2024 11:35:15 +0100 [thread overview]
Message-ID: <5195313b-7071-476d-9506-f65cecf562be@intel.com> (raw)
In-Reply-To: <20240729114719.3461039-1-asasidharan@marvell.com>
[-- Attachment #1: Type: text/plain, Size: 763 bytes --]
On 29-Jul-24 12:47 PM, Aakash Sasidharan wrote:
> In case of event mode operations where event device can help in atomic
> sequence number increment across cores, sequence number need to be
> provided by the application instead of being updated in rte_ipsec or the
> PMD.
>
> To support this, two new APIs rte_ipsec_pkt_crypto_sqn_assign and
> rte_ipsec_pkt_crypto_xprepare are introduced decoupling the seq no update
> functionality from the existing rte_ipsec_pkt_crypto_prepare API.
> Additionally, a new flag ``RTE_IPSEC_SAFLAG_SQN_ASSIGN_DISABLE`` will be
> added to allow disabling of internal sequence number update inside IPsec
> library.
>
> Signed-off-by: Aakash Sasidharan<asasidharan@marvell.com>
> ---
Acked-by: Radu Nicolau <radu.nicolau@intel.com>
[-- Attachment #2: Type: text/html, Size: 1310 bytes --]
prev parent reply other threads:[~2024-07-30 12:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 13:02 [PATCH] " Aakash Sasidharan
2024-07-23 13:37 ` [PATCH v2] " Aakash Sasidharan
2024-07-23 16:04 ` Konstantin Ananyev
2024-07-24 10:16 ` Aakash Sasidharan
2024-07-24 17:08 ` Konstantin Ananyev
2024-07-25 11:23 ` Aakash Sasidharan
2024-07-25 15:52 ` Konstantin Ananyev
2024-07-29 9:54 ` Aakash Sasidharan
2024-07-29 11:47 ` [PATCH v3] " Aakash Sasidharan
2024-07-29 11:53 ` Akhil Goyal
2024-07-31 13:20 ` Thomas Monjalon
2024-07-29 12:00 ` Konstantin Ananyev
2024-07-30 10:09 ` Akhil Goyal
2024-07-30 10:35 ` Radu Nicolau [this message]
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=5195313b-7071-476d-9506-f65cecf562be@intel.com \
--to=radu.nicolau@intel.com \
--cc=anoobj@marvell.com \
--cc=asasidharan@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=vladimir.medvedkin@intel.com \
--cc=vvelumuri@marvell.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).