DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andrzej Ostruszka <amo@semihalf.com>
To: Akhil Goyal <akhil.goyal@nxp.com>,
	Tomasz Duszynski <tdu@semihalf.com>,
	dev@dpdk.org
Cc: Nadav Haklai <nadavh@marvell.com>, mw@semihalf.com
Subject: Re: [dpdk-dev] [PATCH 4/6] crypto/mvsam: add support for AES ECB
Date: Fri, 21 Sep 2018 16:46:01 +0200	[thread overview]
Message-ID: <02bf2f77-0b7a-f0f8-137a-4b246d313164@semihalf.com> (raw)
In-Reply-To: <f8768b00-d698-f1f0-e0f2-1f518c5fee9c@nxp.com>

Akhil

This is ECB mode so AFAIU there is no need for IV as this is not feed
forward/back type of algo and there is nothing extra needed by the first
block (same thing in ccp driver).

I'm leaving this as it is (same for 3DES).

On 17.09.2018 15:59, Akhil Goyal wrote:
> On 8/24/2018 7:24 PM, Tomasz Duszynski wrote:
[...]
>> +	[RTE_CRYPTO_CIPHER_AES_ECB] = {
[...]
>> +				.algo = RTE_CRYPTO_CIPHER_AES_ECB,
>> +				.block_size = 16,
[...]
>> +				.iv_size = {
>> +					.min = 0,
>> +					.max = 0,
>> +					.increment = 0
>> +				}
> iv size may not be zero in this case and also in other patch for 3des. 
> Please check

  reply	other threads:[~2018-09-21 14:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-24 13:54 [dpdk-dev] [PATCH 0/6] crypto/mvsam: add new features and fixes Tomasz Duszynski
2018-08-24 13:54 ` [dpdk-dev] [PATCH 1/6] crypto/mvsam: fix shared library build Tomasz Duszynski
2018-09-17 14:00   ` Akhil Goyal
2018-08-24 13:54 ` [dpdk-dev] [PATCH 2/6] crypto/mvsam: update hash digest sizes Tomasz Duszynski
2018-09-17 13:54   ` Akhil Goyal
2018-08-24 13:54 ` [dpdk-dev] [PATCH 3/6] crypto/mvsam: add support for HMAC SHA224 Tomasz Duszynski
2018-09-17 13:57   ` Akhil Goyal
2018-09-21 14:49     ` Andrzej Ostruszka
2018-08-24 13:54 ` [dpdk-dev] [PATCH 4/6] crypto/mvsam: add support for AES ECB Tomasz Duszynski
2018-09-17 13:59   ` Akhil Goyal
2018-09-21 14:46     ` Andrzej Ostruszka [this message]
2018-08-24 13:54 ` [dpdk-dev] [PATCH 5/6] crypto/mvsam: add support for crypto/auth NULL algorithms Tomasz Duszynski
2018-08-24 13:54 ` [dpdk-dev] [PATCH 6/6] crypto/mvsam: add 3DES ECB to the capabilities list Tomasz Duszynski
2018-09-21 14:53 ` [dpdk-dev] [PATCH v2 0/6] crypto/mvsam: add new features and fixes Andrzej Ostruszka
2018-09-21 14:53   ` [dpdk-dev] [PATCH v2 1/6] crypto/mvsam: fix shared library build Andrzej Ostruszka
2018-09-21 14:53   ` [dpdk-dev] [PATCH v2 2/6] crypto/mvsam: update hash digest sizes Andrzej Ostruszka
2018-09-21 14:53   ` [dpdk-dev] [PATCH v2 3/6] crypto/mvsam: support for HMAC SHA224 Andrzej Ostruszka
2018-09-21 14:53   ` [dpdk-dev] [PATCH v2 4/6] crypto/mvsam: support for AES ECB Andrzej Ostruszka
2018-09-21 14:53   ` [dpdk-dev] [PATCH v2 5/6] crypto/mvsam: support for crypto/auth NULL algorithms Andrzej Ostruszka
2018-09-21 14:53   ` [dpdk-dev] [PATCH v2 6/6] crypto/mvsam: add 3DES ECB to the capabilities list Andrzej Ostruszka
2018-09-25 15:24   ` [dpdk-dev] [PATCH v2 0/6] crypto/mvsam: add new features and fixes Akhil Goyal
2018-09-26 10:03     ` Andrzej Ostruszka
2018-09-26 10:51       ` Akhil Goyal
2018-10-01 13:28   ` 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=02bf2f77-0b7a-f0f8-137a-4b246d313164@semihalf.com \
    --to=amo@semihalf.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=mw@semihalf.com \
    --cc=nadavh@marvell.com \
    --cc=tdu@semihalf.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).