DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Aakash Sasidharan <asasidharan@marvell.com>
Cc: dev@dpdk.org, Jerin Jacob <jerinj@marvell.com>,
	Anoob Joseph <anoobj@marvell.com>,
	Vidya Sagar Velumuri <vvelumuri@marvell.com>,
	Aakash Sasidharan <asasidharan@marvell.com>,
	"konstantin.v.ananyev@yandex.ru" <konstantin.v.ananyev@yandex.ru>,
	"vladimir.medvedkin@intel.com" <vladimir.medvedkin@intel.com>,
	Akhil Goyal <gakhil@marvell.com>
Subject: Re: [PATCH v3] doc: announce rte_ipsec API changes
Date: Wed, 31 Jul 2024 15:20:15 +0200	[thread overview]
Message-ID: <3873129.FjKLVJYuhi@thomas> (raw)
In-Reply-To: <CO6PR18MB44841432C30585D900F5341DD8B72@CO6PR18MB4484.namprd18.prod.outlook.com>

29/07/2024 13:53, Akhil Goyal:
> > Subject: [PATCH v3] doc: announce rte_ipsec API changes
> > 
> > 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: Akhil Goyal <gakhil@marvell.com>

Acked-by: Konstantin Ananyev <konstantin.ananyev@huawei.com>
Acked-by: Radu Nicolau <radu.nicolau@intel.com>

Applied, thanks.



  reply	other threads:[~2024-07-31 13:24 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 [this message]
2024-07-29 12:00     ` Konstantin Ananyev
2024-07-30 10:09     ` Akhil Goyal
2024-07-30 10:35     ` Radu Nicolau

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=3873129.FjKLVJYuhi@thomas \
    --to=thomas@monjalon.net \
    --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).