Re: [dpdk-dev] [PATCH] [RFC] cryptodev: move AES-GMAC to aead algorithms
From: Zhang, Roy Fan <hidden>
Date: 2020-09-01 08:14:25
From: Zhang, Roy Fan <hidden>
Date: 2020-09-01 08:14:25
-----Original Message----- From: Kusztal, ArkadiuszX <redacted> Sent: Wednesday, July 29, 2020 3:22 PM To: dev@dpdk.org Cc: akhil.goyal@nxp.com; Trahe, Fiona <redacted>; anoobj@marvell.com; shallyv@marvell.com; Doherty, Declan [off-list ref]; Zhang, Roy Fan [off-list ref]; Ananyev, Konstantin [off-list ref]; Kusztal, ArkadiuszX [off-list ref] Subject: [PATCH] [RFC] cryptodev: move AES-GMAC to aead algorithms This is proposal to move AES-GMAC algorithm to AEAD set of algorithms. It is however not 100% conformant GMAC as instead of aad pointer data to be authenticated is passed normally and aead.data.length field is used to specify length of data to be authenticated. Reason behind this move is that GMAC is variant of GCM so it may simplify implementations that are using these algorithms (mainly IPsec). AES-GMAC therefore needs to be removed from auth algorithms. Signed-off-by: Arek Kusztal <redacted>
Acked-by: Fan Zhang <redacted>