From: Heiko Schocher <hs@denx.de>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: Scott Wood <scottwood@freescale.com>,
linuxppc-dev@ozlabs.org, Wolfgang Denk <wd@denx.de>
Subject: Re: [PATCH 0/4] 8xx: Optimize TLB Miss code.
Date: Thu, 04 Mar 2010 17:30:07 +0100 [thread overview]
Message-ID: <4B8FE00F.4030405@denx.de> (raw)
In-Reply-To: <OF22F52BE0.FB3F104E-ONC12576DC.00469DB5-C12576DC.004808C4@transmode.se>
Hello Joakim,
Joakim Tjernlund wrote:
> Wolfgang Denk <wd@denx.de> wrote on 2010/03/04 13:16:56:
>> From: Wolfgang Denk <wd@denx.de>
>> To: hs@denx.de
>> Cc: Joakim Tjernlund <joakim.tjernlund@transmode.se>, Klaus-Jürgen
>> <heydeck@kieback-peter.de>, linuxppc-dev@ozlabs.org, Scott Wood
>> <scottwood@freescale.com>
>> Date: 2010/03/04 13:17
>> Subject: Re: [PATCH 0/4] 8xx: Optimize TLB Miss code.
>>
>> 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?
>
> Close but not quite. What stands out most is:
>
> Memory latencies in nanoseconds - smaller is better
> (WARNING - may not be correct, check graphs)
> ------------------------------------------------------------------------------
> Host OS Mhz L1 $ L2 $ Main mem Rand mem Guesses
> --------- ------------- --- ---- ---- -------- -------- -------
> tqm8xx Linux 2.6.33- 66 31.8 141.0 184.0 1165.7
> tqm8xx Linux 2.6.33- 66 31.8 141.2 184.2 1165.3
> tqm8xx Linux 2.6.33- 66 31.8 141.3 184.3 1165.6
> tqm8xx Linux 2.6.33- 66 31.8 141.3 184.2 1166.2
>
> tqm8xx Linux 2.6.33- 66 31.8 141.0 171.8 1100.5 No L2 cache?
> tqm8xx Linux 2.6.33- 66 31.8 141.0 171.8 1102.5 No L2 cache?
> tqm8xx Linux 2.6.33- 66 31.8 141.0 171.8 1101.7 No L2 cache?
> tqm8xx Linux 2.6.33- 66 31.8 141.0 171.8 1101.6 No L2 cache?
>
> tqm8xx Linux 2.6.33- 66 31.8 141.1 173.4 1149.1 No L2 cache?
> tqm8xx Linux 2.6.33- 66 31.8 141.1 173.4 1149.0 No L2 cache?
> tqm8xx Linux 2.6.33- 66 31.7 141.1 173.4 1148.7 No L2 cache?
> tqm8xx Linux 2.6.33- 66 31.7 141.1 173.4 1148.2 No L2 cache?
>
> tqm8xx Linux 2.6.33- 66 31.8 171.1 171.7 1099.8 No L2 cache?
> tqm8xx Linux 2.6.33- 66 31.8 171.1 171.6 1100.5 No L2 cache?
> tqm8xx Linux 2.6.33- 66 31.7 171.0 171.7 1101.0 No L2 cache?
> tqm8xx Linux 2.6.33- 66 31.8 171.0 171.6 1101.3 No L2 cache?
>
>
> Besides the numbers, note how the first group doesn't have a Guesses entry.
> Is there something odd with the results for the first group?
Hmm.. just to be safe, I made this test again, but it shows also no entry in
"Guesses" ... Hardware, Linux Source, rootFS, lmbench sources, all the
same ...
> Also, since you are using MODULES, patch 2 is nullified.
> Patch 1 is very minor and should not show I think.
> This leaves patches 3 & 4.
> There appears to be something funny with patch 3,Don't touch ACCESSED when no SWAP, as
> it yields bad numbers for Prot Fault so perhaps I am missing something that needs ACCESSED
> even if NO_SWAP. Perhaps a someone that knows MM in Linux knows?
> Is there any messages in the kernel log(dmesg)?
I couldn;t find something in the output with dmesg ... but if you
want this output, I can send it to you.
bye
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2010-03-04 16:30 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
2010-03-04 13:06 ` Joakim Tjernlund
2010-03-04 16:30 ` Heiko Schocher [this message]
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=4B8FE00F.4030405@denx.de \
--to=hs@denx.de \
--cc=joakim.tjernlund@transmode.se \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
--cc=wd@denx.de \
/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.