From: Pavel Machek <pavel@ucw.cz>
To: Jan Engelhardt <jengelh@inai.de>
Cc: Theodore Ts'o <tytso@mit.edu>,
Geert Uytterhoeven <geert@linux-m68k.org>,
kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Dhrystone -- userland version
Date: Wed, 11 Jan 2023 16:30:24 +0100 [thread overview]
Message-ID: <Y77WEO43H8eIPA5U@duo.ucw.cz> (raw)
In-Reply-To: <614os9n2-2sq1-2qnr-56q6-1qq628271175@vanv.qr>
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]
Hi!
> >> > However, as this is not Linux-specific, how hard can it be to convince
> >> > your distro to include https://github.com/qris/dhrystone-deb.git?
> >> > Usually, when I have a full userspace available, I just clone the above,
> >> > and debuild it myself.
> >>
> >> Dunno. I'd not solve it if package was in Debian, but it is not.
> >
> >I would suspect the better long-term solution would be to get the
> >package into Debian, since that will be easier for people to use. I
> >suspect the reason why most distros don't include it is because it
> >really is a **terrible** benchmark for most use cases.
>
> (All of) you could install boinc-client and just exercise
> --run_cpu_benchmarks without (I think) attaching to any particular
> computing project. The package should be in distros and you get
> both Dhrystone and Whetstone.
Hehe, nice trick, but it does not work for me:
boinc --run_cpu_benchmarks
does not actually seem to run the benchmarks. Anyway, it is 3MB
project for few kilobytes of benchmarks...
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-11 15:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 22:30 Dhrystone -- userland version 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
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 [this message]
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=Y77WEO43H8eIPA5U@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=geert@linux-m68k.org \
--cc=jengelh@inai.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.