From: Vipin Varghese <vipin.varghese@amd.com>
To: <dev@dpdk.org>, <stable@dpdk.org>, <honest.jiang@foxmail.com>,
<gmuthukrishn@marvell.com>, <ferruh.yigit@amd.com>
Subject: [PATCH] app/dma-perf: add average latency per worker
Date: Tue, 19 Dec 2023 22:10:21 +0530 [thread overview]
Message-ID: <20231219164021.858-1-vipin.varghese@amd.com> (raw)
Modify the user display data with total average latency per worker.
Signed-off-by: Vipin Varghese <vipin.varghese@amd.com>
---
app/test-dma-perf/benchmark.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/app/test-dma-perf/benchmark.c b/app/test-dma-perf/benchmark.c
index 9b1f58c78c..8b6886af62 100644
--- a/app/test-dma-perf/benchmark.c
+++ b/app/test-dma-perf/benchmark.c
@@ -470,7 +470,8 @@ mem_copy_benchmark(struct test_configure *cfg, bool is_dma)
bandwidth_total += bandwidth;
avg_cycles_total += avg_cycles;
}
- printf("\nTotal Bandwidth: %.3lf Gbps, Total MOps: %.3lf\n", bandwidth_total, mops_total);
+ printf("\nAverage Cycles/op: %.2lf, Total Bandwidth: %.3lf Gbps, Total MOps: %.3lf\n",
+ (float) avg_cycles_total / nb_workers, bandwidth_total, mops_total);
snprintf(output_str[MAX_WORKER_NB], MAX_OUTPUT_STR_LEN, CSV_TOTAL_LINE_FMT,
cfg->scenario_id, nr_buf, memory * nb_workers,
avg_cycles_total / nb_workers, bandwidth_total, mops_total);
--
2.34.1
next reply other threads:[~2023-12-19 16:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 16:40 Vipin Varghese [this message]
2024-02-23 9:45 ` fengchengwen
2024-02-27 9:50 ` Varghese, Vipin
2024-02-27 13:09 ` fengchengwen
2024-02-28 3:06 ` Varghese, Vipin
2024-02-28 3:05 ` Varghese, Vipin
2024-03-06 15:06 ` [PATCH v2] " Vipin Varghese
2024-03-08 1:15 ` fengchengwen
2024-03-08 2:39 ` Varghese, Vipin
2024-03-08 19:06 ` [PATCH v3] " Vipin Varghese
2024-03-12 1:53 ` fengchengwen
2024-03-18 2:36 ` Thomas Monjalon
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=20231219164021.858-1-vipin.varghese@amd.com \
--to=vipin.varghese@amd.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=gmuthukrishn@marvell.com \
--cc=honest.jiang@foxmail.com \
--cc=stable@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).