Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@mailhost.uni-koblenz.de>
To: wje@fir.engr.sgi.com (William J. Earl)
Cc: ralf@mailhost.uni-koblenz.de, linux@cthulhu.engr.sgi.com
Subject: Re: Magnum 4000 caches
Date: Thu, 23 Oct 1997 20:23:38 +0200 (MEST)	[thread overview]
Message-ID: <199710231825.UAA26628@informatik.uni-koblenz.de> (raw)
In-Reply-To: <199710231808.LAA11992@fir.engr.sgi.com> from "William J. Earl" at Oct 23, 97 11:08:31 am

>      Yes, I think you should leave the linesize alone, at least on
> the MCT version 2.  You could try alternate linesize values on the MCT
> version 3.  The cache control code should use the linesize values from
> $config.  By the way, I have found that it is generally faster on the R4000 (and
> especially on later processors) to compute such values from $config each
> time than to load them from variables in memory.  The amortized cost
> of the extra cache misses can easily outweigh the extra instructions needed
> to recompute the value (since the latter are really very few, if you
> code the sequence cleverly in assembly language).  Similarly, if you need
> to test for processor type, it is usually faster to fetch and decode
> $prid than to use a variable in memory.

Indeed, Linux could need a little polish in that respect ...

>        The R6000 is a real challenge.  It is substantially different
> from the R3000 and R4000.  In particular, it uses part of the cache
> as a sort of second level TLB.  ES/IX is the CDC version of MP RISC/os.
> (MIPS worked on MP RISC/os, but never shipped it to customers; CDC took
> it over as a product.)  The I/O is fairly straightforward, being mostly
> VME devices, but it does include I/O address mapping hardware which must
> be configured.

Is the information in newer releases of Kane's MIPS bible sufficient to
do the R6000 part of the job?  I guess the company (BIT ???) that made the
R6000 is no longer around, so it would make sense if Roman'd ask them
for a manual ...

  Ralf

WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf@mailhost.uni-koblenz.de>
To: "William J. Earl" <wje@fir.engr.sgi.com>
Cc: ralf@mailhost.uni-koblenz.de, linux@cthulhu.engr.sgi.com
Subject: Re: Magnum 4000 caches
Date: Thu, 23 Oct 1997 20:23:38 +0200 (MEST)	[thread overview]
Message-ID: <199710231825.UAA26628@informatik.uni-koblenz.de> (raw)
Message-ID: <19971023182338.6KjC3_c6ARfyMzM6wuX4QX2rzff3l-9_nI87zQC3IKQ@z> (raw)
In-Reply-To: <199710231808.LAA11992@fir.engr.sgi.com> from "William J. Earl" at Oct 23, 97 11:08:31 am

>      Yes, I think you should leave the linesize alone, at least on
> the MCT version 2.  You could try alternate linesize values on the MCT
> version 3.  The cache control code should use the linesize values from
> $config.  By the way, I have found that it is generally faster on the R4000 (and
> especially on later processors) to compute such values from $config each
> time than to load them from variables in memory.  The amortized cost
> of the extra cache misses can easily outweigh the extra instructions needed
> to recompute the value (since the latter are really very few, if you
> code the sequence cleverly in assembly language).  Similarly, if you need
> to test for processor type, it is usually faster to fetch and decode
> $prid than to use a variable in memory.

Indeed, Linux could need a little polish in that respect ...

>        The R6000 is a real challenge.  It is substantially different
> from the R3000 and R4000.  In particular, it uses part of the cache
> as a sort of second level TLB.  ES/IX is the CDC version of MP RISC/os.
> (MIPS worked on MP RISC/os, but never shipped it to customers; CDC took
> it over as a product.)  The I/O is fairly straightforward, being mostly
> VME devices, but it does include I/O address mapping hardware which must
> be configured.

Is the information in newer releases of Kane's MIPS bible sufficient to
do the R6000 part of the job?  I guess the company (BIT ???) that made the
R6000 is no longer around, so it would make sense if Roman'd ask them
for a manual ...

  Ralf

  reply	other threads:[~1997-10-23 18:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-23 17:05 Magnum 4000 caches Ralf Baechle
1997-10-23 17:21 ` William J. Earl
1997-10-23 17:56   ` Ralf Baechle
1997-10-23 17:56     ` Ralf Baechle
1997-10-23 18:08     ` William J. Earl
1997-10-23 18:23       ` Ralf Baechle [this message]
1997-10-23 18:23         ` Ralf Baechle
1997-10-23 18:47         ` William J. Earl

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=199710231825.UAA26628@informatik.uni-koblenz.de \
    --to=ralf@mailhost.uni-koblenz.de \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=wje@fir.engr.sgi.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