From: Laura Abbott <labbott@redhat.com>
To: Kees Cook <keescook@google.com>, Shuah Khan <shuah@kernel.org>,
Fengguang Wu <fengguang.wu@intel.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>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: collecting simple benchmark scripts?
Date: Thu, 15 Feb 2018 10:32:21 -0800 [thread overview]
Message-ID: <7723ae8d-8333-ba17-6983-a45ec8b11c54@redhat.com> (raw)
In-Reply-To: <CAGXu5j+LVvfdeD4rhTKAQ0PP5s5ysAjNtrfkpcp2sLzwKqbVHw@mail.gmail.com>
On 02/14/2018 02:50 PM, Kees Cook wrote:
> 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.
>
> Or, I guess, at least collecting all the micro-benchmarks in some
> single place, as they're a bit scattered.
>
> I'm sure I'm not remotely the first person to bring this up, but my
> attempts at searches for this have failed.
>
> Thoughts?
>
> -Kees
>
This is the script I've been using for hackbench since it can
be noisy. I expect someone to tell me the math is wrong but
I'd be happy to throw this in a repo if others are interested
#!/bin/sh
CNT=100
mean=0.0
M2=0.0
for i in $(seq 1 $CNT); do
echo $i
r=`hackbench -g 20 -l 1000 | grep Time | cut -d ' ' -f 2`
d_calc="$r-$mean"
d=`echo $d_calc | bc -l`
mean_calc="$mean+($d/$i)"
mean=`echo $mean_calc | bc -l`
M2_calc="$M2+($d*($r-$mean))"
M2=`echo $M2_calc| bc -l`
done
echo "mean $mean"
V_calc="$M2/$(($CNT-1))"
V=`echo $V_calc | bc -l`
DEV_calc="sqrt($V)"
DEV=`echo $DEV_calc | bc -l`
echo "variance $V"
echo "stdev $DEV"
next prev parent reply other threads:[~2018-02-15 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 22:50 Kees Cook
2018-02-14 23:16 ` Tycho Andersen
2018-02-15 18:32 ` Laura Abbott [this message]
2018-02-23 8:06 ` Pavel Machek
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=7723ae8d-8333-ba17-6983-a45ec8b11c54@redhat.com \
--to=labbott@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=keescook@google.com \
--cc=khilman@kernel.org \
--cc=kirill.shutemov@linux.intel.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
all inboxes | Powered by JetHome®