From: Borislav Petkov <bp@alien8.de>
To: John <da_audiophile@yahoo.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Additional compiler optimization options
Date: Thu, 6 Dec 2012 00:08:35 +0100 [thread overview]
Message-ID: <20121205230835.GF6222@liondog.tnic> (raw)
In-Reply-To: <1354748412.17691.YahooMailNeo@web140005.mail.bf1.yahoo.com>
On Wed, Dec 05, 2012 at 03:00:12PM -0800, John wrote:
> > This only makes sense if you can show a noticeable performance
>
> > improvement using one of the those -march options with at least one
> > benchmark from those which we have now in the kernel.
>
> Thank you for the feedback, Boris. Can you point me to the built in
> benchmarks to which you referred? I am interested in probing this
> further.
Maybe the easiest thing to do is build the kernel:
make -j<number_of_cores+1>
in your kernel directory and time it. You could get more precise output
if you trace that workload with perf:
$ perf stat --repeat 10 make -j<number_of_cores+1>
And look at how the perf output looks like.
For all those runs, you need hardware supporting any of these options
and the running kernel should each time be built with a different
optimization option.
This will show us whether differently optimized kernels show any
performance difference.
And then you can go and try other benchmarks like kernbench, hackbench,
etc, whatever your favourite search engine gives you for "linux
benchmarks"
HTH.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2012-12-05 23:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 22:09 John
2012-12-05 22:27 ` Borislav Petkov
2012-12-05 23:00 ` John
2012-12-05 23:08 ` Borislav Petkov [this message]
2012-12-08 12:13 ` [PATCH] Expand CPU compiler options John
2012-12-09 11:18 ` Borislav Petkov
2012-12-09 12:08 ` John
2012-12-09 12:29 ` Borislav Petkov
2012-12-09 12:59 ` John
2012-12-09 13:24 ` Borislav Petkov
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=20121205230835.GF6222@liondog.tnic \
--to=bp@alien8.de \
--cc=da_audiophile@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
/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®