From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Cc: dev@dpdk.org, fiona.trahe@intel.com, deepak.k.jain@intel.com,
pablo.de.lara.guarch@intel.com, john.griffin@intel.com
Subject: Re: [dpdk-dev] [PATCH] app/test: add AES GCM performance test to cryptodev
Date: Fri, 23 Sep 2016 14:36:02 +0800 [thread overview]
Message-ID: <20160923063602.GU23158@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <20160923063257.GT23158@yliu-dev.sh.intel.com>
On Fri, Sep 23, 2016 at 02:32:57PM +0800, Yuanhan Liu wrote:
> On Thu, Sep 22, 2016 at 04:54:57PM +0100, Arek Kusztal wrote:
> > This patch adds AES Galois Counter Mode test case for cryptodev
> > QAT tests. Test is performed with different buffer sizes, burst
> > size of 32 and 128b key. Test vectors are placed in
> > app/test/test_cryptodev_perf_vectors.h file.
> >
> > This patch depends on the following patches/patchsets:
> >
> > "app/test: fix linkage scope of gmac plaintext array"
> > (http://dpdk.org/dev/patchwork/patch/16023/)
> >
> > Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
>
> FYI,
>
> My robot caught a build error when this patch applied.
>
> --yliu
>
> ---
> test_cryptodev.o:(.data+0x1be0): multiple definition of `gmac_plaintext'
> test_cryptodev_perf.o:(.data+0x4a0): first defined here
> collect2: error: ld returned 1 exit status
One more: it breaks 32 bit build.
---
/yeti/vm/ubuntu-initrd-16.04-i386-build/dpdk/app/test/test_cryptodev_perf.c: In function 'perf_AES_GCM':
/yeti/vm/ubuntu-initrd-16.04-i386-build/dpdk/app/test/test_cryptodev_perf.c:3187:10: error: format '%lu' expects argument of type 'long unsigned int', but argument 5 has type 'uint64_t {aka long long unsigned int}' [-Werror=format=]
printf("\n%u\t\t%6.2f\t%16.2f\t%8lu\t%10lu",
^
/yeti/vm/ubuntu-initrd-16.04-i386-build/dpdk/app/test/test_cryptodev_perf.c:3187:10: error: format '%lu' expects argument of type 'long unsigned int', but argument 6 has type 'uint64_t {aka long long unsigned int}' [-Werror=format=]
cc1: all warnings being treated as errors
next prev parent reply other threads:[~2016-09-23 6:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 15:54 Arek Kusztal
2016-09-23 6:32 ` Yuanhan Liu
2016-09-23 6:36 ` Yuanhan Liu [this message]
2016-09-23 9:02 ` Jain, Deepak K
2016-09-23 9:07 ` Kusztal, ArkadiuszX
2016-09-23 9:10 ` Yuanhan Liu
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=20160923063602.GU23158@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=john.griffin@intel.com \
--cc=pablo.de.lara.guarch@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).