DPDK patches and discussions
 help / color / mirror / Atom feed
From: Zhangfei Gao <zhangfei.gao@linaro.org>
To: Akhil Goyal <gakhil@marvell.com>,
	Zhangfei Gao <zhangfei.gao@linaro.org>,
	 Declan Doherty <declan.doherty@intel.com>,
	Fan Zhang <royzhang1980@gmail.com>,
	Ashish Gupta <ashishg@marvell.com>, Ray Kinsella <mdr@ashroe.eu>,
	"thomas@monjalon.net" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "acc@openeuler.org" <acc@openeuler.org>
Subject: Re: [EXT] [PATCH resend v5 5/6] crypto/uadk: support auth algorithms
Date: Wed, 26 Oct 2022 18:02:16 +0800	[thread overview]
Message-ID: <6d05fb62-0e19-508e-638d-72a4d0905e41@linaro.org> (raw)
In-Reply-To: <CO6PR18MB4484C18A2971895659BEEC11D8319@CO6PR18MB4484.namprd18.prod.outlook.com>



On 2022/10/25 下午10:38, Akhil Goyal wrote:
>> Hash algorithms:
>>
>> * ``RTE_CRYPTO_AUTH_MD5``
>> * ``RTE_CRYPTO_AUTH_MD5_HMAC``
>> * ``RTE_CRYPTO_AUTH_SHA1``
>> * ``RTE_CRYPTO_AUTH_SHA1_HMAC``
>> * ``RTE_CRYPTO_AUTH_SHA224``
>> * ``RTE_CRYPTO_AUTH_SHA224_HMAC``
>> * ``RTE_CRYPTO_AUTH_SHA256``
>> * ``RTE_CRYPTO_AUTH_SHA256_HMAC``
>> * ``RTE_CRYPTO_AUTH_SHA384``
>> * ``RTE_CRYPTO_AUTH_SHA384_HMAC``
>> * ``RTE_CRYPTO_AUTH_SHA512``
>> * ``RTE_CRYPTO_AUTH_SHA512_HMAC``
>>
> It is better to rewrite the description as
>
> Support added for MD5, SHA1, SHA224, SHA256, SHA384, SHA512
> Authentication algorithms with and without HMAC.
>
>> Signed-off-by: Zhangfei Gao <zhangfei.gao@linaro.org>
>
>> ---
>>   doc/guides/cryptodevs/features/uadk.ini |  12 +
>>   doc/guides/cryptodevs/uadk.rst          |  15 +
>>   drivers/crypto/uadk/uadk_crypto_pmd.c   | 459 ++++++++++++++++++++++++
>>   3 files changed, 486 insertions(+)
>>
> <Snip>
>
>> @@ -72,6 +84,252 @@ RTE_LOG_REGISTER_DEFAULT(uadk_crypto_logtype,
>> INFO);
>>   		## __VA_ARGS__)
>>
>>   static const struct rte_cryptodev_capabilities uadk_crypto_v2_capabilities[] = {
>> +	{	/* MD5 HMAC */
>> +		.op = RTE_CRYPTO_OP_TYPE_SYMMETRIC,
>> +		{.sym = {
>> +			.xform_type = RTE_CRYPTO_SYM_XFORM_AUTH,
>> +			{.auth = {
>> +				.algo = RTE_CRYPTO_AUTH_MD5_HMAC,
>> +				.block_size = 64,
>> +				.key_size = {
>> +					.min = 0,
>> +					.max = 0,
>> +					.increment = 0
>> +				},
> It seems there is a mistake here.
> Auth algos with HMAC do have keys > 0.
>
> I am not sure if your test cases are getting passed with these capabilities.
>
> Same comment for all the HMAC capabilities.

After double confirmed, and studied the openssl crypto config.
The hash do not have key, so value is 0
But HMAC need key,
After using openssl crypto value,
the passed case increased from 50 to 72, though no reported fail case in 
both case.

Thanks for the reminding.


  reply	other threads:[~2022-10-26 10:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24 13:44 [PATCH resend v5 0/6] crypto/uadk: introduce uadk crypto driver Zhangfei Gao
2022-10-24 13:44 ` [PATCH resend v5 1/6] " Zhangfei Gao
2022-10-25 14:08   ` [EXT] " Akhil Goyal
2022-10-24 13:44 ` [PATCH resend v5 2/6] crypto/uadk: support basic operations Zhangfei Gao
2022-10-25 14:18   ` [EXT] " Akhil Goyal
2022-10-24 13:44 ` [PATCH resend v5 3/6] crypto/uadk: support enqueue/dequeue operations Zhangfei Gao
2022-10-24 13:44 ` [PATCH resend v5 4/6] crypto/uadk: support cipher algorithms Zhangfei Gao
2022-10-25 14:28   ` [EXT] " Akhil Goyal
2022-10-24 13:44 ` [PATCH resend v5 5/6] crypto/uadk: support auth algorithms Zhangfei Gao
2022-10-25 14:38   ` [EXT] " Akhil Goyal
2022-10-26 10:02     ` Zhangfei Gao [this message]
2022-10-24 13:44 ` [PATCH resend v5 6/6] test/crypto: add cryptodev_uadk_autotest Zhangfei Gao
2022-10-25 14:54   ` [EXT] " Akhil Goyal
2022-10-26  9:57     ` Zhangfei Gao
2022-10-25 14:59 ` [EXT] [PATCH resend v5 0/6] crypto/uadk: introduce uadk crypto driver Akhil Goyal
2022-10-26  9:53   ` Zhangfei Gao
2022-10-26 10:16     ` Akhil Goyal

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=6d05fb62-0e19-508e-638d-72a4d0905e41@linaro.org \
    --to=zhangfei.gao@linaro.org \
    --cc=acc@openeuler.org \
    --cc=ashishg@marvell.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=mdr@ashroe.eu \
    --cc=royzhang1980@gmail.com \
    --cc=thomas@monjalon.net \
    /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).