From: "Wan, Zhe" <zhe.wan@intel.com>
To: "Yao, BingX Y" <bingx.y.yao@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Yao, BingX Y" <bingx.y.yao@intel.com>
Subject: Re: [dts] [PATCH V1 2/4] add file to crypto_perf
Date: Mon, 21 Oct 2019 07:39:34 +0000 [thread overview]
Message-ID: <861C16A15685B44AA870C0D2A97B60458A26C3B3@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1571638221-86724-2-git-send-email-bingx.y.yao@intel.com>
Acked-by: Wan, Zhe <zhe.wan@intel.com>
Thanks!
BR,
Wan,Zhe
-----Original Message-----
From: dts <dts-bounces@dpdk.org> On Behalf Of yaobing
Sent: 2019年10月21日 14:10
To: dts@dpdk.org
Cc: Yao, BingX Y <bingx.y.yao@intel.com>
Subject: [dts] [PATCH V1 2/4] add file to crypto_perf
add file to crypto_perf
Signed-off-by: yaobing <bingx.y.yao@intel.com>
---
dep/test_aes_cbc.data | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
create mode 100644 dep/test_aes_cbc.data
diff --git a/dep/test_aes_cbc.data b/dep/test_aes_cbc.data new file mode 100644 index 0000000..c467da4
--- /dev/null
+++ b/dep/test_aes_cbc.data
@@ -0,0 +1,27 @@
+# Global Section
+plaintext =
+0xff, 0xca, 0xfb, 0xf1, 0x38, 0x20, 0x2f, 0x7b, 0x24, 0x98, 0x26, 0x7d,
+0x1d, 0x9f, 0xb3, 0x93, 0xd9, 0xef, 0xbd, 0xad, 0x4e, 0x40, 0xbd, 0x60,
+0xe9, 0x48, 0x59, 0x90, 0x67, 0xd7, 0x2b, 0x7b ciphertext = 0x77, 0xF9,
+0xF7, 0x7A, 0xA3, 0xCB, 0x68, 0x1A, 0x11, 0x70, 0xD8, 0x7A, 0xB6, 0xE2,
+0x37, 0x7E, 0xD1, 0x57, 0x1C, 0x8E, 0x85, 0xD8, 0x08, 0xBF, 0x57, 0x1F,
+0x21, 0x6C, 0xAD, 0xAD, 0x47, 0x1E cipher_key = 0xE4, 0x23, 0x33, 0x8A,
+0x35, 0x64, 0x61, 0xE2, 0x49, 0x03, 0xDD, 0xC6, 0xB8, 0xCA, 0x55, 0x7A,
+0xd0, 0xe7, 0x4b, 0xfb, 0x5d, 0xe5, 0x0c, 0xe7, 0x6f, 0x21, 0xb5, 0x52,
+0x2a, 0xbb, 0xc7, 0xf7 auth_key = 0xaf, 0x96, 0x42, 0xf1, 0x8c, 0x50,
+0xdc, 0x67, 0x1a, 0x43, 0x47, 0x62, 0xc7, 0x04, 0xab, 0x05, 0xf5, 0x0c,
+0xe7, 0xa2, 0xa6, 0x23, 0xd5, 0x3d, 0x95, 0xd8, 0xcd, 0x86, 0x79, 0xf5,
+0x01, 0x47, 0x4f, 0xf9, 0x1d, 0x9d, 0x36, 0xf7, 0x68, 0x1a, 0x64, 0x44,
+0x58, 0x5d, 0xe5, 0x81, 0x15, 0x2a, 0x41, 0xe4, 0x0e, 0xaa, 0x1f, 0x04,
+0x21, 0xff, 0x2c, 0xf3, 0x73, 0x2b, 0x48, 0x1e, 0xd2, 0xf7 cipher_iv =
+0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B,
+0x0C, 0x0D, 0x0E, 0x0F # Section sha 1 hmac buff 32 [sha1_hmac_buff_32]
+digest = 0x36, 0xCA, 0x49, 0x6A, 0xE3, 0x54, 0xD8, 0x4F, 0x0B, 0x76,
+0xD8, 0xAA, 0x78, 0xEB, 0x9D, 0x65, 0x2C, 0xCA, 0x1F, 0x97 # Section
+sha 256 hmac buff 32 [sha256_hmac_buff_32] digest = 0x1C, 0xB2, 0x3D,
+0xD1, 0xF9, 0xC7, 0x6C, 0x49, 0x2E, 0xDA, 0x94, 0x8B, 0xF1, 0xCF, 0x96,
+0x43, 0x67, 0x50, 0x39, 0x76, 0xB5, 0xA1, 0xCE, 0xA1, 0xD7, 0x77, 0x10,
+0x07, 0x43, 0x37, 0x05, 0xB4
--
2.17.2
next prev parent reply other threads:[~2019-10-21 7:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 6:10 [dts] [PATCH V1 1/4] " yaobing
2019-10-21 6:10 ` [dts] [PATCH V1 2/4] " yaobing
2019-10-21 7:39 ` Wan, Zhe [this message]
2019-10-21 7:44 ` Yao, BingX Y
2019-10-21 6:10 ` [dts] [PATCH V1 3/4] add config " yaobing
2019-10-21 7:40 ` Wan, Zhe
2019-10-21 7:45 ` Yao, BingX Y
2019-10-21 6:10 ` [dts] [PATCH V1 4/4] tests/TestSuite_crypto_perf_cryptodev_perf: add cases yaobing
2019-10-21 7:40 ` Wan, Zhe
2019-10-21 7:45 ` Yao, BingX Y
2019-10-21 7:39 ` [dts] [PATCH V1 1/4] add file to crypto_perf Wan, Zhe
2019-10-21 7:42 ` Yao, BingX Y
2019-10-23 9:54 ` 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=861C16A15685B44AA870C0D2A97B60458A26C3B3@SHSMSX103.ccr.corp.intel.com \
--to=zhe.wan@intel.com \
--cc=bingx.y.yao@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).