mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Theodore Ts'o <tytso@mit.edu>
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 08:40:30 +0100	[thread overview]
Message-ID: <Y7pzbnlXgv+asekg@amd.ucw.cz> (raw)
In-Reply-To: <Y7pRw47hidw+s6+g@mit.edu>

[-- Attachment #1: Type: text/plain, Size: 1422 bytes --]

Hi!

> > 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.

Yes, I'm talking about Dhrystone benchmark. We are carrying
kernel-only version in lib/dhry_*.c, it is in -next now.

commit cfbd4cc940275240e97f8b922c8f18a44fe15c07
Author: Geert Uytterhoeven <geert+renesas@glider.be>
Date:   Thu Dec 8 15:31:28 2022 +0100

    lib: add Dhrystone benchmark test

I'd like userspace-too version, at the same place :-).

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 --]

  reply	other threads:[~2023-01-08  7:40 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 [this message]
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=Y7pzbnlXgv+asekg@amd.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@osdl.org \
    --cc=geert+renesas@glider.be \
    --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 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®