[dpdk-dev] [PATCH] cryptodev: fix KASUMI F9 expected parameters

De Lara Guarch, Pablo pablo.de.lara.guarch at intel.com
Fri Jul 14 12:30:44 CEST 2017


Hi,

> -----Original Message-----
> From: Trahe, Fiona
> Sent: Friday, July 14, 2017 10:31 AM
> To: De Lara Guarch, Pablo <pablo.de.lara.guarch at intel.com>; Kusztal,
> ArkadiuszX <arkadiuszx.kusztal at intel.com>; Griffin, John
> <john.griffin at intel.com>; Doherty, Declan <declan.doherty at intel.com>
> Cc: dev at dpdk.org; Trahe, Fiona <fiona.trahe at intel.com>
> Subject: RE: [PATCH] cryptodev: fix KASUMI F9 expected parameters

...

> > diff --git a/lib/librte_cryptodev/rte_crypto_sym.h
> > b/lib/librte_cryptodev/rte_crypto_sym.h
> > index f1b2f38..d4b403b 100644
> > --- a/lib/librte_cryptodev/rte_crypto_sym.h
> > +++ b/lib/librte_cryptodev/rte_crypto_sym.h
> > @@ -343,9 +343,8 @@ struct rte_crypto_auth_xform {
> >  		uint16_t length;
> >  		/**< Length of valid IV data.
> >  		 *
> > -		 * - For KASUMI in F9 mode, SNOW3G in UIA2 mode, for
> > -		 *   ZUC in EIA3 mode and for AES-GMAC, this is the length
> > -		 *   of the IV.
> > +		 * - For SNOW3G in UIA2 mode, for ZUC in EIA3 mode and
> > +		 *   for AES-GMAC, this is the length of the IV.
> 
> [Fiona] I think it's worth adding here:
> For Kasumi in F9 mode the IV field in not used and length should be set to
> 0.

Fair enough, will add that in the v2.

Thanks,
Pablo


More information about the dev mailing list