DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: <dev@dpdk.org>
Cc: Akhil Goyal <gakhil@marvell.com>
Subject: [PATCH] app/crypto-perf: update result granularity
Date: Tue, 5 Aug 2025 12:44:01 +0530	[thread overview]
Message-ID: <20250805071401.207884-1-gakhil@marvell.com> (raw)

In cases like RSA which has low performance numbers
compared to AES, the Mops and gbps may not give accurate results.
Hence updated the number of decimal places to have meaningful
results.
The results are not updated to show Kops or mbps as the results
may be used in CI scripts which considers them as Mops/gbps and
hence all scripts will need to be updated.

Signed-off-by: Akhil Goyal <gakhil@marvell.com>
---
 app/test-crypto-perf/cperf_test_throughput.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/app/test-crypto-perf/cperf_test_throughput.c b/app/test-crypto-perf/cperf_test_throughput.c
index 13b16d9670..3a82d75f95 100644
--- a/app/test-crypto-perf/cperf_test_throughput.c
+++ b/app/test-crypto-perf/cperf_test_throughput.c
@@ -374,7 +374,7 @@ cperf_throughput_test_runner(void *test_ctx)
 					"Cycles/Buf");
 
 			printf("%12u%12u%12u%12"PRIu64"%12"PRIu64"%12"PRIu64
-					"%12"PRIu64"%12.4f%12.4f%12.2f\n",
+					"%12"PRIu64"%12.6f%12.6f%12.2f\n",
 					ctx->lcore_id,
 					ctx->options->test_buffer_size,
 					test_burst_size,
@@ -394,7 +394,7 @@ cperf_throughput_test_runner(void *test_ctx)
 					"Cycles/Buf\n\n");
 
 			printf("%u,%u,%u,%"PRIu64",%"PRIu64",%"PRIu64",%"PRIu64","
-					"%.3f,%.3f,%.3f\n",
+					"%.6f,%.6f,%.3f\n",
 					ctx->lcore_id,
 					ctx->options->test_buffer_size,
 					test_burst_size,
-- 
2.25.1


                 reply	other threads:[~2025-08-05  7:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20250805071401.207884-1-gakhil@marvell.com \
    --to=gakhil@marvell.com \
    --cc=dev@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).