> -----Original Message----- > From: Gonzalez Monroy, Sergio > Sent: Friday, June 30, 2017 2:52 PM > To: De Lara Guarch, Pablo <pablo.de.lara.gua...@intel.com>; Doherty, > Declan <declan.dohe...@intel.com> > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH 1/2] crypto/aesni_mb: support IPSec Multi- > buffer lib v0.46 > > On 28/06/2017 12:48, Pablo de Lara wrote: > > IPSec Multi-buffer library v0.46 has been released, which includes, > > among othe features, support for 12-byte IV, for AES-CTR, keeping also > > the previous 16-byte IV, for backward compatibility reasons. > > > > Signed-off-by: Pablo de Lara <pablo.de.lara.gua...@intel.com> > > --- > > doc/guides/cryptodevs/aesni_mb.rst | 18 +++++++++++++++++- > > doc/guides/rel_notes/release_17_08.rst | 6 ++++++ > > drivers/crypto/aesni_mb/rte_aesni_mb_pmd_ops.c | 4 ++-- > > 3 files changed, 25 insertions(+), 3 deletions(-) > > > > diff --git a/doc/guides/cryptodevs/aesni_mb.rst > > b/doc/guides/cryptodevs/aesni_mb.rst > > index ecb52a1..fafcd9f 100644 > > --- a/doc/guides/cryptodevs/aesni_mb.rst > > +++ b/doc/guides/cryptodevs/aesni_mb.rst > > @@ -69,6 +69,9 @@ Limitations > > * Chained mbufs are not supported. > > * Only in-place is currently supported (destination address is the same > as source address). > > * Only supports session-oriented API implementation (session-less APIs > are not supported). > > +* If IV is passed with 16 bytes, last 4 bytes will be ignored, as > > +underlying library only > > + requires 12 bytes and will append 4 bytes (counter) at the end. > > + The library always set these 4 bytes to 1, as IPSec requires counter to > be set to 1. > > I don't think the text above is correct.
Forgot to remove that, well spotted! Will send a v2 shortly. Thanks, Pablo
