From: Borislav Petkov <bp@alien8.de>
To: John <da_audiophile@yahoo.com>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"david.heidelberger@ixit.cz" <david.heidelberger@ixit.cz>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"x86@kernel.org" <x86@kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] expand micro-optimizations in kernel to newer model CPUs
Date: Sun, 15 Dec 2013 14:23:29 +0100 [thread overview]
Message-ID: <20131215132329.GC4361@pd.tnic> (raw)
In-Reply-To: <1387111370.81380.YahooMailNeo@web140001.mail.bf1.yahoo.com>
On Sun, Dec 15, 2013 at 04:42:50AM -0800, John wrote:
> I am using ANOVA to establish that the generic group differs from the
> optimized group.
You probably should run a couple other benchmarks, in addition, for
greater confidence that this optimization actually brings any palpable
improvement and is not just causing code bloat.
For example, last time I did a perf profile of a kernel build on AMD
F15h, the PILERDRIVER "optimization" was actually even a bit worse than
the standard MK8 one.
http://marc.info/?l=linux-kernel&m=138081947417204
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-12-15 13:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 15:53 [PATCH] expand micro-optimizations in kernel to newer model CPUs John
2013-12-10 3:51 ` David Heidelberger
2013-12-13 12:37 ` Austin S Hemmelgarn
[not found] ` <1387051250.86178.YahooMailNeo@web140005.mail.bf1.yahoo.com>
[not found] ` <ce679ca5-bf83-4c2a-9234-859cc7a4206b@email.android.com>
[not found] ` <1387057337.97000.YahooMailNeo@web140004.mail.bf1.yahoo.com>
[not found] ` <52ACECC4.208@zytor.com>
2013-12-15 12:00 ` John
2013-12-15 12:27 ` Richard Weinberger
2013-12-15 12:42 ` John
2013-12-15 13:23 ` Borislav Petkov [this message]
2013-12-15 17:31 ` Richard Weinberger
2013-12-16 14:28 ` Ingo Molnar
2013-12-17 12:59 ` Austin S Hemmelgarn
2013-12-15 12:23 ` John
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=20131215132329.GC4361@pd.tnic \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=da_audiophile@yahoo.com \
--cc=david.heidelberger@ixit.cz \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=richard.weinberger@gmail.com \
--cc=tglx@linutronix.de \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.