From: Pavel Machek <pavel@ucw.cz>
To: Kees Cook <keescook@google.com>
Cc: Shuah Khan <shuah@kernel.org>,
Fengguang Wu <fengguang.wu@intel.com>,
Laura Abbott <labbott@redhat.com>,
Tycho Andersen <tycho@tycho.ws>,
Steven Rostedt <srostedt@redhat.com>,
Kevin Hilman <khilman@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: collecting simple benchmark scripts?
Date: Fri, 23 Feb 2018 09:06:53 +0100 [thread overview]
Message-ID: <20180223080653.GA1584@amd> (raw)
In-Reply-To: <CAGXu5j+LVvfdeD4rhTKAQ0PP5s5ysAjNtrfkpcp2sLzwKqbVHw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]
Hi!
> In a separate thread, some folks were looking for some simple
> benchmarks for evaluating various changes to kernel internals (as
> opposed to the much more focused things like xfstests). For me, this
> has been an area of lore and passed-around scripts, and it seems like
> maybe we should have a subdirectory of tools/testing/benchmarks/ or
> something to collect these?
>
> (Or maybe this already exists and I've totally missed it?)
>
> I've got at least one micro-benchmark in
> tools/testing/selftests/seccomp/seccomp_benchmark.c, and searches show
> tools/testing/selftests/vm/gup_benchmark.c too, but I was thinking of
> either more generali things more like the famous "kernel build
> benchmark" or a wrapper for running hackbench to get some statistics
> out of it, etc.
Ok, I guess my micro-benchmark is too micro for you, but I like to use
"time cat /dev/urandom | head -c 10000000 | bzip2 -9 - | wc -c"
I have a page with various results online somewhere, probably at
http://atrey.karlin.mff.cuni.cz/~pavel/quickbench.html
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2018-02-23 8:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 22:50 collecting simple benchmark scripts? Kees Cook
2018-02-14 23:16 ` Tycho Andersen
2018-02-15 18:32 ` Laura Abbott
2018-02-23 8:06 ` Pavel Machek [this message]
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=20180223080653.GA1584@amd \
--to=pavel@ucw.cz \
--cc=fengguang.wu@intel.com \
--cc=keescook@google.com \
--cc=khilman@kernel.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=srostedt@redhat.com \
--cc=tglx@linutronix.de \
--cc=tycho@tycho.ws \
/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