From: Pavel Machek <pavel@ucw.cz>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Willy Tarreau <w@1wt.eu>, Theodore Ts'o <tytso@mit.edu>,
kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Dhrystone -- userland version
Date: Mon, 9 Jan 2023 20:51:44 +0100 [thread overview]
Message-ID: <Y7xwUKE64PfPRMt7@duo.ucw.cz> (raw)
In-Reply-To: <CAMuHMdWm8Z-xkDUTjppbPT_uxFqfdOZPrPYxgBNgFRL6E=sN3w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]
Hi!
> > count=1666675 us50=20178 us250=99913 diff=79735 cpu_MHz=4180.536 tsc50=42614718 tsc250=211016124 diff=101 rdtsc_MHz=2112.014
> >
> > It's also what's used by sbc-bench to verify that CPU vendors are not
> > cheating in the embedded world. It's very simple, and not arch-dependent
> > nor compiler-dependent (at least as long as you don't build at -O0 :-)).
>
> Seeing the rdtsc stuff, I was a bit skeptical, but it seems to work
> fine on arm32 and rv64.
>
> Unfortunately you forgot to add a LICENSE file ;-)
>
> Alternatively, I can use the C version of BogoMIPS. Which has its
> own merits and reputation.
I'd expect BogoMIPS to be _much_ worse than Dhrystone. If all the
cores are same, it should be good enough, but...
> The nice thing about Dhrystones is that people still publish numbers
> for comparison, also DMIPS/MHz and DMIPS/mW.
...and there seems to be no replacement for that. Dhrystones seem to
become the standard in RISC-V community at least.
Best regards,
Pavel
--
People of Russia, stop Putin before his war on Ukraine escalates.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2023-01-09 19:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 22:30 Pavel Machek
2023-01-08 5:16 ` Theodore Ts'o
2023-01-08 7:40 ` Pavel Machek
2023-01-08 9:58 ` Geert Uytterhoeven
2023-01-08 18:47 ` Pavel Machek
2023-01-09 0:45 ` Theodore Ts'o
2023-01-09 9:28 ` Geert Uytterhoeven
2023-01-09 14:30 ` Willy Tarreau
2023-01-09 19:36 ` Geert Uytterhoeven
2023-01-09 19:51 ` Pavel Machek [this message]
2023-01-09 19:59 ` Geert Uytterhoeven
2023-01-09 21:36 ` Willy Tarreau
2023-01-09 19:57 ` Geert Uytterhoeven
2023-01-09 14:59 ` Pavel Machek
2023-01-11 13:32 ` Jan Engelhardt
2023-01-11 13:52 ` Geert Uytterhoeven
2023-01-11 15:30 ` Pavel Machek
2023-01-11 16:32 ` Jan Engelhardt
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=Y7xwUKE64PfPRMt7@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®