Re: [dpdk-dev] Crypto API for AES-XTS cipher algorithm

2021-02-02 Thread Matan Azrad
Yes. I'll do soon. From: Akhil Goyal Sent: Thursday, January 21, 2021 8:33 PM To: Matan Azrad ; Declan Doherty Cc: dev@dpdk.org Subject: RE: Crypto API for AES-XTS cipher algorithm External email: Use caution opening links or attachments Hi Matan, Can you send an RFC patch for the changes you

Re: [dpdk-dev] Crypto API for AES-XTS cipher algorithm

2021-01-21 Thread Akhil Goyal
Hi Matan, Can you send an RFC patch for the changes you are looking forward in the cryptodev lib. Regards, Akhil From: Matan Azrad Sent: Thursday, January 21, 2021 11:16 PM To: Akhil Goyal ; Declan Doherty Cc: dev@dpdk.org Subject: RE: Crypto API for AES-XTS cipher algorithm Hi Akhil Yes, y

Re: [dpdk-dev] Crypto API for AES-XTS cipher algorithm

2021-01-21 Thread Matan Azrad
Hi Akhil Yes, you right regards terms of data-unit and block size. My intention was for data-unit. AES-XTS algorithm is a mode of AES so by definition the block size is 16B. So, no need capability for it. Also in the symmetric operation structure, the `length` field is described as next: /**< T

Re: [dpdk-dev] Crypto API for AES-XTS cipher algorithm

2021-01-18 Thread Akhil Goyal
Hi Matan, Block size is specified in the capability structure and is expected to be same for a particular algorithm. And for AES-XTS it is 16 bytes only if I am not wrong. As per my understanding, data unit is different from block size. Data unit is the input data which may or may not be multipl