No need as API is still experimental.
Howver I'd suggest changing the subject to
"declare crypto asym xform immutable"
non-reusable is confusing as the session and xform will be re-used on all the
ops associated with the session.
From: Ayuj Verma [mailto:ayve...@marvell.com]
Sent: Friday, July 1
Hi Akhil, Arek, Fiona,
Since this require changes in other Asym PMD( qat) apart from openssl (we plan
to send changes for this),
so should we need to send any announcement on ABI breakage here before
proposing patch v1?
Thanks and regards
Ayuj Verma
From: A
Hi Arek,
Please see inline.
Thanks and regards
Ayuj Verma
From: Kusztal, ArkadiuszX
Sent: 17 July 2019 19:40
To: Ayuj Verma; akhil.go...@nxp.com
Cc: Trahe, Fiona; Shally Verma; Sunila Sahu; Kanaka Durga Kotamarthy;
dev@dpdk.org
Subject: RE: [RFC] mark asym
Hi Ayuj,
> -Original Message-
> From: Ayuj Verma [mailto:ayve...@marvell.com]
> Sent: Wednesday, July 17, 2019 2:34 PM
> To: akhil.go...@nxp.com
> Cc: Kusztal, ArkadiuszX ; Trahe, Fiona
> ; shal...@marvell.com; ss...@marvell.com;
> kkotamar...@marvell.com; dev@dpdk.org; Ayuj Verma
>
> Sub
This RFC proposes changes in asymmetric session usability of
transform structure. In current implementation asym xform is
seen as temporary entity that can be re-used by application
once sessions are initialized with it.
This enforces PMD to copy all key buffers during session setup
time. Since li
5 matches
Mail list logo
