When using CSV, the output of the throughput performance numbers
was not correct, representing decimal numbers incorrectly.

Fixes: f8be1786b1b8 ("app/crypto-perf: introduce performance test application")
Cc: sta...@dpdk.org

Signed-off-by: Pablo de Lara <pablo.de.lara.gua...@intel.com>
---
 app/test-crypto-perf/cperf_test_throughput.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/app/test-crypto-perf/cperf_test_throughput.c 
b/app/test-crypto-perf/cperf_test_throughput.c
index f1a8dcc..5ba75d0 100644
--- a/app/test-crypto-perf/cperf_test_throughput.c
+++ b/app/test-crypto-perf/cperf_test_throughput.c
@@ -485,14 +485,14 @@ cperf_throughput_test_runner(void *test_ctx)
                                        cycles_per_packet);
                } else {
                        if (!only_once)
-                               printf("# lcore id, Buffer Size(B),"
+                               printf("#lcore id,Buffer Size(B),"
                                        "Burst Size,Enqueued,Dequeued,Failed 
Enq,"
                                        "Failed 
Deq,Ops(Millions),Throughput(Gbps),"
                                        "Cycles/Buf\n\n");
                        only_once = 1;
 
-                       
printf("%10u;%10u;%u;%"PRIu64";%"PRIu64";%"PRIu64";%"PRIu64";"
-                                       "%.f3;%.f3;%.f3\n",
+                       
printf("%u;%u;%u;%"PRIu64";%"PRIu64";%"PRIu64";%"PRIu64";"
+                                       "%.3f;%.3f;%.3f\n",
                                        ctx->lcore_id,
                                        ctx->options->test_buffer_size,
                                        test_burst_size,
-- 
2.9.4

Reply via email to