test suite reviews and discussions
 help / color / mirror / Atom feed
From: xinfengx <xinfengx.zhao@intel.com>
To: dts@dpdk.org
Cc: xinfengx <xinfengx.zhao@intel.com>
Subject: [dts] [PATCH V1 1/3] test_plans: add aes-docsisbpi algorithm into crypto_perf test plan
Date: Fri, 15 May 2020 16:03:30 +0800	[thread overview]
Message-ID: <20200515080332.102832-2-xinfengx.zhao@intel.com> (raw)
In-Reply-To: <20200515080332.102832-1-xinfengx.zhao@intel.com>

Signed-off-by: xinfengx <xinfengx.zhao@intel.com>
---
 test_plans/crypto_perf_cryptodev_perf_test_plan.rst | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/test_plans/crypto_perf_cryptodev_perf_test_plan.rst b/test_plans/crypto_perf_cryptodev_perf_test_plan.rst
index 4975934..1044506 100644
--- a/test_plans/crypto_perf_cryptodev_perf_test_plan.rst
+++ b/test_plans/crypto_perf_cryptodev_perf_test_plan.rst
@@ -58,6 +58,8 @@ Part of the algorithms are not supported currently.
 +-----------+-------------------+---------------------------------------------------------------------------+
 | aes       | ctr               | Encrypt/Decrypt;Key size: 128, 192, 256 bits                              |
 +-----------+-------------------+---------------------------------------------------------------------------+
+| aes       | docsisbpi         | Encrypt/Decrypt;Key size: 128, 256 bits                                   |
++-----------+-------------------+---------------------------------------------------------------------------+
 | sha       |                   | sha1, sha2-224, sha2-384, sha2-256, sha2-512                              |
 +-----------+-------------------+---------------------------------------------------------------------------+
 | hmac      |                   | Support md5 and sha implementations sha1, sha2-224, sha2-256,             |
@@ -86,6 +88,8 @@ Part of the algorithms are not supported currently.
 +---------+-------------------+---------------------------------------------------------------------------+
 | aes     | ctr               |  Encrypt/Decrypt;Key size: 128, 192, 256 bits                             |
 +---------+-------------------+---------------------------------------------------------------------------+
+| aes     | docsisbpi         |  Encrypt/Decrypt;Key size: 128, 256 bits                                  |
++---------+-------------------+---------------------------------------------------------------------------+
 | 3des    | cbc               |  Encrypt/Decrypt;Key size: 128, 192 bits                                  |
 +---------+-------------------+---------------------------------------------------------------------------+
 | 3des    | ctr               |  Encrypt/Decrypt;Key size: 128, 192 bits                                  |
-- 
2.17.1


  reply	other threads:[~2020-05-15  8:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15  8:03 [dts] [PATCH V1 0/3] add new test cases for aes-docsisbpi xinfengx
2020-05-15  8:03 ` xinfengx [this message]
2020-05-15  8:03 ` [dts] [PATCH V1 2/3] tests: add " xinfengx
2020-05-15  8:03 ` [dts] [PATCH V1 3/3] conf: add test setting for aes-docsisbpi cases xinfengx
2020-05-27  8:07   ` Wan, Zhe
2020-05-26  7:45 ` [dts] [PATCH V1 0/3] add new test cases for aes-docsisbpi Zhao, XinfengX
2020-06-01  7:46 ` Tu, Lijuan

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=20200515080332.102832-2-xinfengx.zhao@intel.com \
    --to=xinfengx.zhao@intel.com \
    --cc=dts@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).