test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Liu, Yong" <yong.liu@intel.com>
To: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>,  "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH] tests l2fwd_crypto: add sha224 and sha384 algorithm check
Date: Sun, 18 Sep 2016 14:58:49 +0800	[thread overview]
Message-ID: <57DE3B29.5080004@intel.com> (raw)
In-Reply-To: <9DEEADBC57E43F4DA73B571777FECECA3A58EDDC@shsmsx102.ccr.corp.intel.com>

Applied into master branch.

On 09/18/2016 02:03 PM, Chen, Zhaoyan wrote:
>> -----Original Message-----
>> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Marvin Liu
>> Sent: Sunday, September 18, 2016 1:15 PM
>> To: dts@dpdk.org
>> Cc: Liu, Yong <yong.liu@intel.com>
>> Subject: [dts] [PATCH] tests l2fwd_crypto: add sha224 and sha384 algorithm
>> check
>>
>> Signed-off-by: Marvin Liu <yong.liu@intel.com>
>>
>> diff --git a/tests/TestSuite_l2fwd_crypto.py
>> b/tests/TestSuite_l2fwd_crypto.py index 76f60ba..3dd5344 100644
>> --- a/tests/TestSuite_l2fwd_crypto.py
>> +++ b/tests/TestSuite_l2fwd_crypto.py
>> @@ -152,11 +152,21 @@ class TestL2fwdCrypto(TestCase):
>>                   test_vectors, "qat_h_SHA1_HMAC_01"):
>>               result = False
>>
>> +        self.logger.info("Test qat_h_SHA224_HMAC_01")
>> +        if not self.__execute_l2fwd_crypto_test(
>> +                test_vectors, "qat_h_SHA224_HMAC_01"):
>> +            result = False
>> +
>>           self.logger.info("Test qat_h_SHA256_HMAC_01")
>>           if not self.__execute_l2fwd_crypto_test(
>>                   test_vectors, "qat_h_SHA256_HMAC_01"):
>>               result = False
>>
>> +        self.logger.info("Test qat_h_SHA384_HMAC_01")
>> +        if not self.__execute_l2fwd_crypto_test(
>> +                test_vectors, "qat_h_SHA384_HMAC_01"):
>> +            result = False
>> +
>>           self.logger.info("Test qat_h_SHA512_HMAC_01")
>>           if not self.__execute_l2fwd_crypto_test(
>>                   test_vectors, "qat_h_SHA512_HMAC_01"):
>> @@ -547,6 +557,25 @@ test_vectors = {
>>           "output_hash": "12E2EF8B7EBFE556C73307B04E1E46D12BA34884"
>>       },
>>
>> +    "qat_h_SHA224_HMAC_01": {
>> +        "vdev": "",
>> +        "chain": "HASH_ONLY",
>> +        "cdev_type": "ANY",
>> +        "cipher_algo": "",
>> +        "cipher_op": "",
>> +        "cipher_key": "",
>> +        "iv": "",
>> +        "auth_algo": "SHA224_HMAC",
>> +        "auth_op": "GENERATE",
>> +        "auth_key":
>> "000102030405060708090a0b0c0d0e0f000102030405060708090a0b0c0d0e0f00
>> 0102030405060708090a0b0c0d0e0f000102030405060708090a0b0c0d0e0f",
>> +        "auth_key_random_size": "",
>> +        "aad": "",
>> +        "aad_random_size": "",
>> +        "input":
>> "111111111111111111111111111111111111111111111111111111111111111111
>> 11111111111111111111111111111100000000000000000000000000000000",
>> +        "output_cipher": "",
>> +        "output_hash":
>> "45BBF9A798501F225E2C9671863B96BF2DD1C5DAC5DB554A7B9BDB6D"
>> +    },
>> +
>>       "qat_h_SHA256_HMAC_01": {
>>           "vdev": "",
>>           "chain": "HASH_ONLY",
>> @@ -566,6 +595,26 @@ test_vectors = {
>>           "output_hash":
>> "AC9E0BA3A0716F4F4A2734B407BE28D6F276CE0472B827D6EE47B7E518C2BC0
>> D"
>>       },
>>
>> +    "qat_h_SHA384_HMAC_01": {
>> +        "vdev": "",
>> +        "chain": "HASH_ONLY",
>> +        "cdev_type": "ANY",
>> +        "cipher_algo": "",
>> +        "cipher_op": "",
>> +        "cipher_key": "",
>> +        "iv": "",
>> +        "auth_algo": "SHA384_HMAC",
>> +        "auth_op": "GENERATE",
>> +        "auth_key":
>> "000102030405060708090a0b0c0d0e0f000102030405060708090a0b0c0d0e0f00
>> 0102030405060708090a0b0c0d0e0f000102030405060708090a0b0c0d0e0f00010
>> 2030405060708090a0b0c0d0e0f000102030405060708090a0b0c0d0e0f00010203
>> 0405060708090a0b0c0d0e0f000102030405060708090a0b0c0d0e0f",
>> +        "auth_key_random_size": "",
>> +        "auth_key_random_size": "",
>> +        "aad": "",
>> +        "aad_random_size": "",
>> +        "input":
>> "111111111111111111111111111111111111111111111111111111111111111111
>> 11111111111111111111111111111100000000000000000000000000000000",
>> +        "output_cipher": "",
>> +        "output_hash":
>> "2CE1BD8F18A93A63AF04C21EDE42EE4D8468C6DFD17474B64D2C36E6CAA9F9
>> D177B424F91DAB8D2D4CAF2AAF63FFAE09"
>> +    },
>> +
>>       "qat_h_SHA512_HMAC_01": {
>>           "vdev": "",
>>           "chain": "HASH_ONLY",
>> --
>> 1.9.3
> Acked-by: Zhaoyan Chen <Zhaoyan.chen@intel.com>

      reply	other threads:[~2016-09-18  6:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-18  5:15 Marvin Liu
2016-09-18  6:03 ` Chen, Zhaoyan
2016-09-18  6:58   ` Liu, Yong [this message]

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=57DE3B29.5080004@intel.com \
    --to=yong.liu@intel.com \
    --cc=dts@dpdk.org \
    --cc=zhaoyan.chen@intel.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).