> -----Original Message----- > From: Kusztal, ArkadiuszX <arkadiuszx.kusz...@intel.com> > Sent: Wednesday, July 29, 2020 3:22 PM > To: dev@dpdk.org > Cc: akhil.go...@nxp.com; Trahe, Fiona <fiona.tr...@intel.com>; > ano...@marvell.com; shal...@marvell.com; Doherty, Declan > <declan.dohe...@intel.com>; Zhang, Roy Fan <roy.fan.zh...@intel.com>; > Ananyev, Konstantin <konstantin.anan...@intel.com>; Kusztal, ArkadiuszX > <arkadiuszx.kusz...@intel.com> > 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 <arkadiuszx.kusz...@intel.com>
Acked-by: Fan Zhang <roy.fan.zh...@intel.com>
