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 19:56:06 +0200 (MEST)	[thread overview]
Message-ID: <199710231757.TAA25739@informatik.uni-koblenz.de> (raw)
In-Reply-To: <199710231721.KAA10794@fir.engr.sgi.com> from "William J. Earl" at Oct 23, 97 10:21:41 am

>      It turned out that, at least for some workloads, the 4000PC
> worked better that way.  (If I remember correctly, a 32-byte linesize
> is better for the icache, since a 4-instruction basic block is
> unusual.)  However, not all boxes use the same linesize values,
> because there were hardware bugs with at least some of the memory
> controllers which were affected by the choice of linesize.  I don't
> remember the details anymore, although I might find them in my mail
> archivies.  I have a 4000PC system (32-byte I, 16-byte D, MCT version 3)
> and two 4000SC systems (16-byte I, D, and S, MCT version 2) still online.
> I think that MCT version 2 would not support a 32-byte line.

So as the easy solution, as I understand things we should be safe by
just leaving the linesize as the firmware chooses them for us Magnums?  
I actually intended to experiment with the linesize on R4k but as
things look now this isn't a good thing.

Btw, seems we'll get an interesting new target for Linux.  It's currently
ftp.uni-erlangen.de and one of the admins who might do the job, a Linux/68k
hacker told me it's a 3 x R6000 box with 256mb of RAM currently running
ES/IX something like that ...

  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 19:56:06 +0200 (MEST)	[thread overview]
Message-ID: <199710231757.TAA25739@informatik.uni-koblenz.de> (raw)
Message-ID: <19971023175606.-HC36U1NQOGLPYIbvDG6QE5TWw1FfsUxT-SGOAOUdZ0@z> (raw)
In-Reply-To: <199710231721.KAA10794@fir.engr.sgi.com> from "William J. Earl" at Oct 23, 97 10:21:41 am

>      It turned out that, at least for some workloads, the 4000PC
> worked better that way.  (If I remember correctly, a 32-byte linesize
> is better for the icache, since a 4-instruction basic block is
> unusual.)  However, not all boxes use the same linesize values,
> because there were hardware bugs with at least some of the memory
> controllers which were affected by the choice of linesize.  I don't
> remember the details anymore, although I might find them in my mail
> archivies.  I have a 4000PC system (32-byte I, 16-byte D, MCT version 3)
> and two 4000SC systems (16-byte I, D, and S, MCT version 2) still online.
> I think that MCT version 2 would not support a 32-byte line.

So as the easy solution, as I understand things we should be safe by
just leaving the linesize as the firmware chooses them for us Magnums?  
I actually intended to experiment with the linesize on R4k but as
things look now this isn't a good thing.

Btw, seems we'll get an interesting new target for Linux.  It's currently
ftp.uni-erlangen.de and one of the admins who might do the job, a Linux/68k
hacker told me it's a 3 x R6000 box with 256mb of RAM currently running
ES/IX something like that ...

  Ralf

  reply	other threads:[~1997-10-23 17:59 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 [this message]
1997-10-23 17:56     ` Ralf Baechle
1997-10-23 18:08     ` William J. Earl
1997-10-23 18:23       ` Ralf Baechle
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=199710231757.TAA25739@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