From: Akhil Goyal <akhil.goyal@nxp.com>
To: Matan Azrad <matan@nvidia.com>,
Declan Doherty <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Crypto API for AES-XTS cipher algorithm
Date: Mon, 18 Jan 2021 15:27:21 +0000 [thread overview]
Message-ID: <VI1PR04MB31686C764F2134AFCA288B17E6A40@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <MW2PR12MB249297C44BE9D6C23399AB28DFA40@MW2PR12MB2492.namprd12.prod.outlook.com>
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 multiple of block size. There are different handling of data
Unit defined if it a multiple of block size or not. And I believe there is limitation for the max value of data unit
Which the driver can give error if it does not support that particular size.
Regards,
Akhil
From: Matan Azrad <matan@nvidia.com>
Sent: Monday, January 18, 2021 8:19 PM
To: Declan Doherty <declan.doherty@intel.com>; Akhil Goyal <akhil.goyal@nxp.com>
Cc: dev@dpdk.org
Subject: Crypto API for AES-XTS cipher algorithm
Hi Declan, Akhil
We are going to implement mlx5 crypto PMD to support AES-XTS de\encrypt operations.
The algorithm defines block size >= 16Bytes (it is called also data-unit)which should be known for encryption\decryptions.
I didn't find this parameter in the cypher xform.
How do you suggest to add it? maybe I'm missing something?
Matan
next prev parent reply other threads:[~2021-01-18 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 14:48 Matan Azrad
2021-01-18 15:27 ` Akhil Goyal [this message]
2021-01-21 17:45 ` Matan Azrad
2021-01-21 18:33 ` Akhil Goyal
2021-02-02 14:10 ` Matan Azrad
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=VI1PR04MB31686C764F2134AFCA288B17E6A40@VI1PR04MB3168.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).