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 applic
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 r
Hi Radu,
Can you ack this deprecation notice if not issues?
> 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
> 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
>
> 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
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_cr
6 matches
Mail list logo
