app/crypto-perf: do not populate the mbufs at init
authorPablo de Lara <pablo.de.lara.guarch@intel.com>
Wed, 4 Oct 2017 03:46:11 +0000 (04:46 +0100)
committerPablo de Lara <pablo.de.lara.guarch@intel.com>
Thu, 12 Oct 2017 14:14:45 +0000 (15:14 +0100)
commit8e4b860141a1f794aafa0494939d2df223bf43b6
treed5cc6c161e8594caa2e4a217c8f97dccfd20abb0
parent5b2b0a740fba32db438d92390a4a853d3af2381c
app/crypto-perf: do not populate the mbufs at init

For throughput and latency tests, it is not required
to populate the mbufs with any test vector.
For verify test, there is already a function that rewrites
the mbufs every time they are going to be used with
crypto operations.

Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
app/test-crypto-perf/cperf_test_common.c