Movatterモバイル変換

This is the mail archive of thelibc-alpha@sourceware.orgmailing list for theglibc project.

Re: [PATCH] Add math benchmark latency test

• From: Siddhesh Poyarekar <siddhesh at gotplt dot org>
• To: Szabolcs Nagy <szabolcs dot nagy at arm dot com>, Wilco Dijkstra <Wilco dot Dijkstra at arm dot com>, "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>
• Cc: nd at arm dot com
• Date: Wed, 16 Aug 2017 19:52:53 +0530
• Subject: Re: [PATCH] Add math benchmark latency test
• Authentication-results: sourceware.org; auth=none
• References: <DB6PR0801MB20530E94B6016F1E3F7CEDEC83820@DB6PR0801MB2053.eurprd08.prod.outlook.com> <0e008f2e-f41a-1bb8-803c-2f798e2c3541@gotplt.org> <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 iscalled, so calls/unit time for throughput and time/call for latency.BTW, this will only work for functions that have the same first argumentand return types.  This is OK for now, but it might be something to fixin future.  A comment to that effect in the code would be very usefulbecause I'm pretty sure I'll forget about it in the next 15 minutes orso and Wilco will too, maybe later than that :)Siddhesh

• Follow-Ups:
  • Re: [PATCH] Add math benchmark latency test
    • From: Wilco Dijkstra

• References:
  • [PATCH] Add math benchmark latency test
    • From: Wilco Dijkstra
  • Re: [PATCH] Add math benchmark latency test
    • From: Siddhesh Poyarekar
  • Re: [PATCH] Add math benchmark latency test
    • From: Szabolcs Nagy