From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Szabolcs Nagy <szabolcs.nagy@arm.com>,
Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Cc: nd@arm.com
Subject: Re: [PATCH] Add math benchmark latency test
Date: Wed, 16 Aug 2017 14:23:00 -0000 [thread overview]
Message-ID: <67d4a047-268c-72a1-1011-85358815237e@gotplt.org> (raw)
In-Reply-To: <59944C03.6070804@arm.com>
On Wednesday 16 August 2017 07:13 PM, Szabolcs Nagy wrote:
> yes in principle the throughput is number of calls/unit time,
> but the inverse of that is just as useful, it's the rate at
> which calls can be issued and then it can be easily compared
> to the latency number, but i guess printing it as calls/sec
> would work too.
I don't dispute its utility, I'd just like it to match what it is
called, so calls/unit time for throughput and time/call for latency.
BTW, this will only work for functions that have the same first argument
and return types. This is OK for now, but it might be something to fix
in future. A comment to that effect in the code would be very useful
because I'm pretty sure I'll forget about it in the next 15 minutes or
so and Wilco will too, maybe later than that :)
Siddhesh
next prev parent reply other threads:[~2017-08-16 14:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 11:26 Wilco Dijkstra
2017-08-16 13:07 ` Siddhesh Poyarekar
2017-08-16 13:43 ` Szabolcs Nagy
2017-08-16 14:23 ` Siddhesh Poyarekar [this message]
2017-08-17 15:46 ` Wilco Dijkstra
2017-08-16 14:23 ` Arjan van de Ven
2017-08-16 14:26 ` Siddhesh Poyarekar
2017-08-16 14:33 ` Arjan van de Ven
2017-08-16 14:36 ` Siddhesh Poyarekar
2017-08-16 14:39 ` Alexander Monakov
2017-08-16 15:22 ` Wilco Dijkstra
2017-08-16 21:01 ` Siddhesh Poyarekar
2017-08-17 13:08 ` [PATCH v3] " Wilco Dijkstra
2017-08-17 14:01 ` Siddhesh Poyarekar
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=67d4a047-268c-72a1-1011-85358815237e@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=Wilco.Dijkstra@arm.com \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.com \
--cc=szabolcs.nagy@arm.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 read-only IMAP folder(s) and NNTP newsgroup(s).