From: David Jander <david.jander@protonic.nl>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Kernel 2.6 on MPC8xx performance trouble...
Date: Mon, 31 Oct 2005 17:29:57 +0200 [thread overview]
Message-ID: <200510311629.57608.david.jander@protonic.nl> (raw)
In-Reply-To: <200510311408.41691.david.jander@protonic.nl>
On Monday 31 October 2005 14:08, David Jander wrote:
> On Monday 31 October 2005 13:58, Mark Chambers wrote:
> >[...]
> >
> > > No, sir, no cache detected !
> > >
> > > Where do I have to look now?
> >
> > Could the cache be in writethrough mode? (Instead of writeback)
>
> Good point. I just checked the same test, but reading instead of writing.
> Same result, no cache detected.
>
> I know how to change cache policy in u-boot, but does the kernel change
> that? If so, where?
Sorry for the stupid question. I did not remember it was there right before my
eyes. It seems I just got lost in the new menu structure of the Kconfig.
And yes, cache was in writethrough mode!!
It seems as though this option disables cache entirely, because after turning
it on, I suddenly get 2.4-type speed measurements.
With CONFIG_8xx_COPYBACK undefined, both reading and writing gives results as
if there was simply no cache. Shouldn't it at least speed up memory-read
access?
Sorry to everone for wasting their time with this stupid mistake of mine.
Thanks for all the help anyway.
Greetings,
--
David Jander
prev parent reply other threads:[~2005-10-31 15:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 6:57 Kernel 2.6 on MPC8xx performance trouble David Jander
2005-10-28 9:36 ` Roger Larsson
2005-10-28 10:57 ` David Jander
2005-10-28 18:44 ` Roger Larsson
2005-10-28 20:37 ` Wolfgang Denk
2005-10-31 9:31 ` David Jander
2005-10-28 15:30 ` Marcelo Tosatti
2005-10-31 8:21 ` David Jander
2005-10-31 12:58 ` Mark Chambers
2005-10-31 13:08 ` David Jander
2005-10-31 15:29 ` David Jander [this message]
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=200510311629.57608.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).