From: David Jander <david.jander@protonic.nl>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Stable Linux kernel 2.6 for MPC8XX
Date: Tue, 14 Mar 2006 15:58:28 +0100 [thread overview]
Message-ID: <200603141558.29155.david.jander@protonic.nl> (raw)
In-Reply-To: <409257f58f9dab82d72ccd997516f772@embeddedalley.com>
On Tuesday 14 March 2006 15:01, Dan Malek wrote:
> On Mar 14, 2006, at 2:50 AM, David Jander wrote:
> > I don't know why, but while everyone still says 2.6 is slower, I am
> > consistently getting results that seem to prove the opposite. Why?
>
> Because this is a compiler test and not an OS test. The
> newer ELDK with 2.6 has better compilers.
No. Please read the cited e-mail entirely before jumping to such a conclusion.
I used the same ELDK for both kernels, and I didn't recompile the nbench
binary ever again after the first time.
The reasons are different, still unknown and apparently my fault. See my
previous post responding to WG.
Sorry to all for the confusion, looks like I must learn to be more careful
when benchmarking.
To keep the answer short: nbench performs exactly the same on both kernels, as
one would expect, since nbench doesn't stress the kernel. I was looking at
incorrect results, trying to blame the cache/tlb management... I was just
wrong, sorry.
Greetings,
--
David Jander
next prev parent reply other threads:[~2006-03-14 14:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 14:29 Stable Linux kernel 2.6 for MPC8XX Fillod Stephane
2006-03-10 7:22 ` David Jander
2006-03-10 13:16 ` Dan Malek
2006-03-10 15:33 ` Wolfgang Denk
2006-03-14 7:50 ` David Jander
2006-03-14 11:56 ` Carlos Mitidieri
2006-03-14 14:01 ` Dan Malek
2006-03-14 14:58 ` David Jander [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-14 8:34 Wolfgang Grandegger
2006-03-14 14:46 ` David Jander
2006-02-28 8:50 Minor bug in file irq.h Laurent Lagrange
2006-03-08 14:32 ` Stable Linux kernel 2.6 for MPC8XX Laurent Lagrange
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=200603141558.29155.david.jander@protonic.nl \
--to=david.jander@protonic.nl \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).