From: "Tu, Lijuan" <lijuan.tu@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 1/4] add file to crypto_perf
Date: Wed, 23 Oct 2019 09:54:07 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BB45AA9@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1571638221-86724-1-git-send-email-bingx.y.yao@intel.com>
Applied the series, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of yaobing
> Sent: Monday, October 21, 2019 2:10 PM
> To: dts@dpdk.org
> Cc: Yao, BingX Y <bingx.y.yao@intel.com>
> Subject: [dts] [PATCH V1 1/4] add file to crypto_perf
>
> add file to crypto_perf
>
> Signed-off-by: yaobing <bingx.y.yao@intel.com>
> ---
> dep/test_aes_gcm.data | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
> create mode 100644 dep/test_aes_gcm.data
>
> diff --git a/dep/test_aes_gcm.data b/dep/test_aes_gcm.data new file mode
> 100644 index 0000000..034f4fa
> --- /dev/null
> +++ b/dep/test_aes_gcm.data
> @@ -0,0 +1,19 @@
> +# Global Section
> +plaintext =
> +0x11, 0x11, 0x11, 0x11, 0x11, 0x11, 0x11, 0x11, 0x11, 0x11, 0x11, 0x11,
> +0x11, 0x11, 0x11, 0x11, 0x11, 0x11, 0x11, 0x11, 0x11, 0x11, 0x11, 0x11,
> +0x11, 0x11, 0x11, 0x11, 0x11, 0x11, 0x11, 0x11
> +
> +ciphertext =
> +0x82, 0x7d, 0xb6, 0xdf, 0x77, 0x0a, 0xe6, 0x45, 0x5a, 0xc3, 0x70, 0x9b,
> +0x27, 0xb2, 0x61, 0x19, 0xa2, 0x37, 0x0b, 0xf7, 0x42, 0xfc, 0xec, 0xe7,
> +0xf7, 0x30, 0xe0, 0x3c, 0x05, 0x55, 0xb3, 0x7d
> +
> +aead_key =
> +0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B,
> +0x0C, 0x0D, 0x0E, 0x0F aead_iv = 0x00, 0x01, 0x02, 0x03, 0x04, 0x05,
> +0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B aead_aad = 0x00, 0x01, 0x02, 0x03,
> +0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B, 0x0C, 0x0D, 0x0E, 0x0F
> +
> +[aes_gcm_buff_32]
> +digest =
> +0x0f, 0xb2, 0x98, 0x59, 0x48, 0xbf, 0x6c, 0x37, 0x5a, 0xad, 0xcd, 0x97,
> +0x9f, 0xbb, 0xc8, 0x2a
> --
> 2.17.2
prev parent reply other threads:[~2019-10-23 9:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 6:10 yaobing
2019-10-21 6:10 ` [dts] [PATCH V1 2/4] " yaobing
2019-10-21 7:39 ` Wan, Zhe
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 [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=8CE3E05A3F976642AAB0F4675D0AD20E0BB45AA9@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@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).