From: Adrian Cox <adrian@humboldt.co.uk>
To: "Hager, Johannes, HRD/AB" <johannes.hager@eads.com>
Cc: "PPC Linux Mailing List (E-Mail)" <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: No L2 Cache on PReP Machine
Date: Thu, 19 Aug 2004 10:44:29 +0100 [thread overview]
Message-ID: <1092908669.10314.81.camel@localhost> (raw)
In-Reply-To: <2D9AB865A49FD511914700105A0EF679016C49C2@morse.smart.lfk.eads.net>
On Thu, 2004-08-19 at 10:04, Hager, Johannes, HRD/AB wrote:
> I have a test program on VxWorks which takes about 110 ms for execution on
> the MVME3604 with enable L2 cache
> I ported this application to a RTAI module and did the test on linux and it
> took about 420ms
> So i disabled the L2 cache in VxWorks and did the test again and then it
> took with VxWorks about 417ms.
> After this and because of the content from /proc/cpuinfo I decided that the
> L2 cache is not used.
That's very convincing.
If you have the source of your VxWorks BSP it may be worth looking for
code where VxWorks enables the L2 cache. You'll need to add a MVME3604
specific patch to your kernel to turn the cache on. I've just looked at
prep_setup.c, and there are already lots of board specific L2 handling
routines, but none for MVME3604.
- Adrian Cox
Humboldt Solutions Ltd.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-08-19 9:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 9:04 No L2 Cache on PReP Machine Hager, Johannes, HRD/AB
2004-08-19 9:44 ` Adrian Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-19 7:43 Hager, Johannes, HRD/AB
2004-08-19 8:56 ` Adrian Cox
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=1092908669.10314.81.camel@localhost \
--to=adrian@humboldt.co.uk \
--cc=johannes.hager@eads.com \
--cc=linuxppc-embedded@lists.linuxppc.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).