public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	geert+renesas@glider.be, Andrew Morton <akpm@osdl.org>
Subject: Re: Dhrystone -- userland version
Date: Sun, 8 Jan 2023 00:16:51 -0500	[thread overview]
Message-ID: <Y7pRw47hidw+s6+g@mit.edu> (raw)
In-Reply-To: <Y7nyd4hPeXsdiibH@duo.ucw.cz>

On Sat, Jan 07, 2023 at 11:30:15PM +0100, Pavel Machek wrote:
> 
> Distributions do not usually carry dhrystone, and I don't think anyone
> really maintains it. It is useful tool, and it seems we'll maintain
> it.
> 
> I'd like to add enough glue so that it would be runnable from
> userspace, too? Userland version is what is actually useful to me, and
> it should not be hard.

I don't see whatever message you were replying to, and it doesn't seem
to be archived in lore[1], so I'm not sure about the context.  But you
are talking about the Dhrystone benchmark[2], right?

[1] https://lore.kernel.org/all/Y7nyd4hPeXsdiibH@duo.ucw.cz/T/#u
[2] https://wiki.cdot.senecacollege.ca/wiki/Dhrystone_howto

If so, I'm confused what you mean by "add enough glue so that it would
be runnable from userspace" --- Dhrystone is a userspace benchmark,
dating from the 1980's, although what it benchmarks is often more about
the compiler than the CPU's performace.

   "When first released, the Dhrystone benchmark fulfilled a useful
   function – at least it gave an alternative indicator to vendors’
   literal MIPS ratings. However, more than twenty years later, there
   are undoubtedly better benchmarks available for measuring processor
   performance."

						- Ted

  reply	other threads:[~2023-01-08  5:32 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 [this message]
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
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=Y7pRw47hidw+s6+g@mit.edu \
    --to=tytso@mit.edu \
    --cc=akpm@osdl.org \
    --cc=geert+renesas@glider.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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