DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Varghese, Vipin" <vipin.varghese@amd.com>
To: fengchengwen <fengchengwen@huawei.com>, dev@dpdk.org
Cc: ferruh.yigit@amd.com, neerav.parikh@amd.com
Subject: Re: [PATCH v2] app/dma-perf: add average latency per worker
Date: Fri, 8 Mar 2024 08:09:55 +0530	[thread overview]
Message-ID: <230a4d93-211a-45b8-a226-b188b765bdb3@amd.com> (raw)
In-Reply-To: <0526dd9f-aeda-af3f-fd94-70392bd13fab@huawei.com>

[-- Attachment #1: Type: text/plain, Size: 892 bytes --]

<snipped>
>> -     printf("\nTotal Bandwidth: %.3lf Gbps, Total MOps: %.3lf\n", bandwidth_total, mops_total);
>> +     printf("\nAverage Cycles/op per worker: %.1f, Total Bandwidth: %.3lf Gbps, Total MOps: %.3lf\n",
>> +                     (avg_cycles_total * (float) 1.0) / 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);
> As previous mentioned, please make sure the csv format and the above snprintf also modified (make sure stdout and csv has the same value).

Hi Chengwen, the CSV_TOTAL_LINE_FMT already has `Cycles/op` with `%u`. I 
think you are asking to convert this to `%0.1f`to keep it same as `printf`.

Sure I will share v3 for the same.

[-- Attachment #2: Type: text/html, Size: 1698 bytes --]

  reply	other threads:[~2024-03-08  2:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19 16:40 [PATCH] " Vipin Varghese
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 [this message]
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=230a4d93-211a-45b8-a226-b188b765bdb3@amd.com \
    --to=vipin.varghese@amd.com \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=ferruh.yigit@amd.com \
    --cc=neerav.parikh@amd.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).