From: Wolfgang Denk <wd@denx.de>
To: hs@denx.de
Cc: Scott Wood <scottwood@freescale.com>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/4] 8xx: Optimize TLB Miss code.
Date: Thu, 04 Mar 2010 13:16:56 +0100 [thread overview]
Message-ID: <20100304121656.6758A28BBC@gemini.denx.de> (raw)
In-Reply-To: <4B8F8BB4.6070201@denx.de>
Dear Heiko,
thanks for running the tests.
In message <4B8F8BB4.6070201@denx.de> you wrote:
>
> here the results:
>
> run version
>
> 1-4 2.6.33-rc6 without your patches
> 5-8 2.6.33-rc6 with all your patches
> 9-12 2.6.33-rc6 with patches 1,2 and 4 (without 8xx: Don't touch ACCESSED when no SWAP)
> 13-16 2.6.33-rc6 with all your patches and CONFIG_PIN_TLB=y
So CONFIG_PIN_TLB imroves the performance as expected, while the other
patches don;t show any measurable improvememt - or am I reading the
results incorrectly?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
And now remains That we find out the cause of this effect, Or rather
say, the cause of this defect... -- Hamlet, Act II, Scene 2
next prev parent reply other threads:[~2010-03-04 12:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 8:02 [PATCH 0/4] 8xx: Optimize TLB Miss code Heiko Schocher
2010-03-03 8:48 ` Joakim Tjernlund
2010-03-03 8:59 ` Joakim Tjernlund
2010-03-03 10:10 ` Heiko Schocher
2010-03-03 10:38 ` Joakim Tjernlund
2010-03-04 10:30 ` Heiko Schocher
2010-03-04 12:16 ` Wolfgang Denk [this message]
2010-03-04 13:06 ` Joakim Tjernlund
2010-03-04 16:30 ` Heiko Schocher
2010-03-05 10:40 ` Joakim Tjernlund
2010-03-08 7:46 ` Heiko Schocher
2010-03-08 8:44 ` Joakim Tjernlund
2010-03-08 9:06 ` Heiko Schocher
2010-03-08 10:42 ` Joakim Tjernlund
2010-03-09 6:30 ` Wolfgang Denk
2010-03-07 16:03 ` Joakim Tjernlund
-- strict thread matches above, loose matches on Subject: below --
2010-03-02 15:37 Joakim Tjernlund
2010-02-26 8:29 Joakim Tjernlund
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=20100304121656.6758A28BBC@gemini.denx.de \
--to=wd@denx.de \
--cc=hs@denx.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
/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).