> > >
> > > Hi,
> > > > AAD offset in AES-GCM crypto test was calculated by adding 16-byte
> > > > alignment after the IV, which is only needed in AES-CCM.
> > >
> > > Agreed that CCM has a requirement for 16B alignment.
> > > But for GCM, does it break any protocol? Can we not align to byte
> > >
> -Original Message-
> From: Shani Peretz
> Sent: Wednesday, 26 March 2025 9:14
> To: Akhil Goyal ; dev@dpdk.org
> Cc: Suanming Mou ; sta...@dpdk.org; Brian
> Dooley ; Pablo de Lara
>
> Subject: RE: [EXTERNAL] [PATCH] app/crypto-perf: fix aad offset alignment
> -Original Message-
> From: Akhil Goyal
> Sent: Monday, 17 March 2025 12:23
> To: Shani Peretz ; dev@dpdk.org
> Cc: Suanming Mou ; sta...@dpdk.org; Brian
> Dooley ; Pablo de Lara
>
> Subject: RE: [EXTERNAL] [PATCH] app/crypto-perf: fix aad offset alignment
Hi,
> AAD offset in AES-GCM crypto test was calculated by adding
> 16-byte alignment after the IV, which is only needed in AES-CCM.
Agreed that CCM has a requirement for 16B alignment.
But for GCM, does it break any protocol? Can we not align to byte boundary for
performance?
This is a performanc
AAD offset in AES-GCM crypto test was calculated by adding
16-byte alignment after the IV, which is only needed in AES-CCM.
The patch correct the AAD offset calculation in AES-GCM algorithm tests.
Fixes: 0b242422d385 ("app/crypto-perf: set AAD after the crypto operation")
Cc: sta...@dpdk.org
Sig
5 matches
Mail list logo
