Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Florian Lohoff <flo@rfc822.org>,
	linux-mips@linux-mips.org
Subject: Re: [patch] blast_scache nop for sc cpus without scache
Date: Mon, 27 Jun 2005 16:36:33 +0200	[thread overview]
Message-ID: <20050627143633.GD28082@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.61L.0506271309500.15406@blysk.ds.pg.gda.pl>

On Mon, Jun 27, 2005 at 01:45:39PM +0100, Maciej W. Rozycki wrote:

>  Anyway these days we apparently ignore the result of the S-cache probe 
> and the sc_present variable.  The only values that determine whether an 
> S-cache is present or not are: cpu_has_dc_aliases, cpu_has_ic_fills_f_dc 
> and cpu_has_subset_pcaches which you need to get right for your 
> configuration -- I guess cpu_has_dc_aliases == 0, cpu_has_ic_fills_f_dc == 
> 1 and cpu_has_subset_pcaches == 0 should be right to fulfil your needs 
> (but it may break elsewhere).  Have I heard: "serious brain damage" from 
> you?  Well, I couldn't agree more...

What matters isn't the presence of a second level cache but the actual
properties.  The old code was relying almost exclusively on the precense
of an S-cache, so had to be very liberal in it's assumption about that
cache's properties.  Performancewise that sucked, badly.

  Ralf

  reply	other threads:[~2005-06-27 14:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-25 13:19 [patch] blast_scache nop for sc cpus without scache Florian Lohoff
2005-06-25 16:03 ` Ralf Baechle
2005-06-25 17:50   ` Thomas Bogendoerfer
2005-06-27 12:45     ` Maciej W. Rozycki
2005-06-27 14:36       ` Ralf Baechle [this message]
2005-06-27 15:31         ` Maciej W. Rozycki
2005-06-27 19:09       ` Thomas Bogendoerfer
2005-06-27 19:43         ` Maciej W. Rozycki
2005-06-28  7:20           ` peter fuerst
2005-06-28  9:11             ` Maciej W. Rozycki
2005-06-28  9:35               ` Stanislaw Skowronek

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=20050627143633.GD28082@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=flo@rfc822.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.org \
    --cc=tsbogend@alpha.franken.de \
    /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