From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: karthikeyan natarajan <karthik_96cse@yahoo.com>,
linux-mips@linux-mips.org
Subject: Re: How to configure the cache size in r4000
Date: Tue, 13 Jan 2004 17:35:43 +0100 [thread overview]
Message-ID: <20040113163543.GA31459@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.55.0401121345490.21851@jurand.ds.pg.gda.pl>
On Mon, Jan 12, 2004 at 01:51:55PM +0100, Maciej W. Rozycki wrote:
> > The cache size is modified by setting the IC/DC
> > bits in the 'config' register. Seems they are set only
> > by the hardware during the processor reset. And also,
> > those bits are mentioned as read only bits..
>
> You cannot modify the size of the primary caches -- the values are
> hardwired to the amount of cache available in the processor (8kB+8kB for
> the original R4000). However, if you take appropriate precautions, you
> can alter the line sizes of the caches by modifying appropriate bits of
> cp0.config.
On some systems that's a dangerous and won't work due to some issue with
the memory controller. That's why Linux supports all possible combinations
instead of reconfiguring caches. Of course there's also the hope that
developers of a system did configure the cache for the optimal performance.
The one system I recall where reconfiguring is not possible are certain
revs of MIPS Magnum 4000 / MIPS Millenium / Olivetti M700-10 but I'm
convinced there are others.
If reconfiguring is possible 32-byte D-cache and I-Cache lines are probably
the optimum for non-tiny systems. For the L2 cache I'd guess 64 or 128
byte lines.
Ralf
next prev parent reply other threads:[~2004-01-13 16:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-11 12:48 How to configure the cache size in r4000 karthikeyan natarajan
2004-01-12 12:51 ` Maciej W. Rozycki
2004-01-13 16:35 ` Ralf Baechle [this message]
2004-01-13 16:48 ` Maciej W. Rozycki
2004-01-15 9:48 ` Ralf Baechle
2004-01-15 13:31 ` Maciej W. Rozycki
2004-01-15 14:14 ` Current 2.4 CVS (2.4.24-pre2) doesn't boot on SGI Indy Dominik 'Rathann' Mierzejewski
2004-01-15 14:20 ` Dominik 'Rathann' Mierzejewski
2004-01-15 17:19 ` Martin Boehme
2004-01-15 23:17 ` Dominik 'Rathann' Mierzejewski
2004-01-16 1:03 ` Kumba
2004-01-16 1:26 ` Jun Sun
2004-01-16 11:50 ` Dominik 'Rathann' Mierzejewski
2004-01-20 13:06 ` Dominik 'Rathann' Mierzejewski
2004-01-20 16:28 ` Dominik 'Rathann' Mierzejewski
2004-01-23 16:14 ` Dominik 'Rathann' Mierzejewski
2004-01-26 16:31 ` [patch] pg-r4k.c bugs for R4600 rev.2.0 Maciej W. Rozycki
2004-01-26 17:00 ` Ralf Baechle
2004-01-28 1:37 ` Ralf Baechle
2004-01-28 16:22 ` Dominik 'Rathann' Mierzejewski
2004-01-12 16:57 ` How to configure the cache size in r4000 Ralf Baechle
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=20040113163543.GA31459@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=karthik_96cse@yahoo.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
/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