DPDK patches and discussions
 help / color / mirror / Atom feed
From: Fan Zhang <roy.fan.zhang@intel.com>
To: dev@dpdk.org
Cc: declan.doherty@intel.com
Subject: [dpdk-dev] [PATCH 0/5] app/test: rework crypto AES unit test
Date: Tue, 31 May 2016 10:09:44 +0100	[thread overview]
Message-ID: <1464685789-8386-1-git-send-email-roy.fan.zhang@intel.com> (raw)

This patchset reworks the crypto AES unit test by introducing a new
unified test function.

This patchset depends on the following patches:
"qat: add AES counter mode capability"
(http://dpdk.org/dev/patchwork/patch/12464/)
 
"app/test: add test cases for AES CTR"
(http://dpdk.org/dev/patchwork/patch/12465/)
 
"Add AES Counter mode support for AES-NI MB PMD"
(http://dpdk.org/dev/patchwork/patch/12398/)
 
"aesni_mb: add counter mode support:
(http://dpdk.org/dev/patchwork/patch/12399/)
 
"app/test: add aes-ni multi-buffer pmd test cases for AES CTR"
(http://dpdk.org/dev/patchwork/patch/12400/)

Fan Zhang (5):
  app/test: categorize crypto AES test vectors into new file
  app/test: add unified crypto aes test
  app/test: utilize new unified crypto AES test function
  app/test: add crypto AES-CBC-128 HMAC-SHA224 and HMAC-SHA384 unit
    tests
  examples/l2fwd-crypto: enable AES counter mode cipher algorithm

 app/test/Makefile                              |    1 +
 app/test/test_cryptodev.c                      | 1613 ++----------------------
 app/test/test_cryptodev_aes.c                  |  688 ++++++++++
 app/test/test_cryptodev_aes.h                  | 1124 +++++++++++++++++
 app/test/test_cryptodev_aes_ctr_test_vectors.h |  257 ----
 examples/l2fwd-crypto/main.c                   |    1 +
 6 files changed, 1936 insertions(+), 1748 deletions(-)
 create mode 100755 app/test/test_cryptodev_aes.c
 create mode 100755 app/test/test_cryptodev_aes.h
 delete mode 100644 app/test/test_cryptodev_aes_ctr_test_vectors.h

-- 
2.5.5

             reply	other threads:[~2016-05-31  9:09 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-31  9:09 Fan Zhang [this message]
2016-05-31  9:09 ` [dpdk-dev] [PATCH 1/5] app/test: categorize crypto AES test vectors into new file Fan Zhang
2016-05-31  9:09 ` [dpdk-dev] [PATCH 2/5] app/test: add unified crypto aes test Fan Zhang
2016-06-07 20:00   ` Thomas Monjalon
2016-05-31  9:09 ` [dpdk-dev] [PATCH 3/5] app/test: utilize new unified crypto AES test function Fan Zhang
2016-05-31  9:09 ` [dpdk-dev] [PATCH 4/5] app/test: add crypto AES-CBC-128 HMAC-SHA224 and HMAC-SHA384 unit tests Fan Zhang
2016-05-31  9:09 ` [dpdk-dev] [PATCH 5/5] examples/l2fwd-crypto: enable AES counter mode cipher algorithm Fan Zhang
2016-06-07 20:03 ` [dpdk-dev] [PATCH 0/5] app/test: rework crypto AES unit test Thomas Monjalon
2016-06-08 15:38 ` [dpdk-dev] [PATCH v2 0/4] " Fan Zhang
2016-06-08 15:38   ` [dpdk-dev] [PATCH v2 1/4] app/test: categorize crypto AES test vectors into new file Fan Zhang
2016-06-08 15:38   ` [dpdk-dev] [PATCH v2 2/4] app/test: add unified crypto aes test Fan Zhang
2016-06-08 15:38   ` [dpdk-dev] [PATCH v2 3/4] app/test: utilize new unified crypto AES test function Fan Zhang
2016-06-08 15:38   ` [dpdk-dev] [PATCH v2 4/4] app/test: add crypto AES-CBC-128 HMAC-SHA224 and HMAC-SHA384 unit tests Fan Zhang
2016-06-13 12:53   ` [dpdk-dev] [PATCH v3 0/4] app/test: rework crypto AES unit test Fan Zhang
2016-06-13 12:53     ` [dpdk-dev] [PATCH v3 1/4] app/test: categorize crypto AES test vectors into new file Fan Zhang
2016-06-13 12:53     ` [dpdk-dev] [PATCH v3 2/4] app/test: add unified crypto aes test Fan Zhang
2016-06-13 12:53     ` [dpdk-dev] [PATCH v3 3/4] app/test: utilize new unified crypto AES test function Fan Zhang
2016-06-13 12:53     ` [dpdk-dev] [PATCH v3 4/4] app/test: add crypto AES-CBC-128 HMAC-SHA224 and HMAC-SHA384 unit tests Fan Zhang
2016-06-13 14:08     ` [dpdk-dev] [PATCH v4 0/4] app/test: rework crypto AES unit test Fan Zhang
2016-06-13 14:08       ` [dpdk-dev] [PATCH v4 1/4] app/test: categorize crypto AES test vectors into new file Fan Zhang
2016-06-13 14:08       ` [dpdk-dev] [PATCH v4 2/4] app/test: add unified crypto aes test Fan Zhang
2016-06-13 14:08       ` [dpdk-dev] [PATCH v4 3/4] app/test: utilize new unified crypto AES test function Fan Zhang
2016-06-13 14:08       ` [dpdk-dev] [PATCH v4 4/4] app/test: add crypto AES-CBC-128 HMAC-SHA224 and HMAC-SHA384 unit tests Fan Zhang
2016-06-13 20:26       ` [dpdk-dev] [PATCH v4 0/4] app/test: rework crypto AES unit test Thomas Monjalon
2016-06-14  9:57       ` [dpdk-dev] [PATCH v5 0/2] " Fan Zhang
2016-06-14  9:57         ` [dpdk-dev] [PATCH v5 1/2] app/test: reworks the " Fan Zhang
2016-06-15 10:41           ` De Lara Guarch, Pablo
2016-06-21  2:57             ` Chen, Zhaoyan
2016-06-14  9:57         ` [dpdk-dev] [PATCH v5 2/2] app/test: add crypto AES-CBC-128 HMAC-SHA224 and HMAC-SHA384 unit tests Fan Zhang
2016-06-15 11:02         ` [dpdk-dev] [PATCH v6 0/2] rework crypto AES unit test Fan Zhang
2016-06-15 11:02           ` [dpdk-dev] [PATCH v6 1/2] app/test: rework the " Fan Zhang
2016-06-15 11:02           ` [dpdk-dev] [PATCH v6 2/2] app/test: add crypto AES-CBC-128 HMAC-SHA224 and HMAC-SHA384 unit tests Fan Zhang
2016-06-15 12:50           ` [dpdk-dev] [PATCH v6 0/2] rework crypto AES unit test De Lara Guarch, Pablo
2016-06-20 15:18             ` Thomas Monjalon

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=1464685789-8386-1-git-send-email-roy.fan.zhang@intel.com \
    --to=roy.fan.zhang@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    /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).