From: Keith M Wesolowski <wesolows@foobazco.org>
To: Jun Sun <jsun@mvista.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: RFC: Cleanup/detection patch
Date: Thu, 5 Apr 2001 14:03:39 -0700 [thread overview]
Message-ID: <20010405140338.A1508@foobazco.org> (raw)
In-Reply-To: <3ACCD599.1765FCB2@mvista.com>; from jsun@mvista.com on Thu, Apr 05, 2001 at 01:29:13PM -0700
On Thu, Apr 05, 2001 at 01:29:13PM -0700, Jun Sun wrote:
> I don't like bc_ops idea. Usually the external cache capability is still
> integral part of the CPU.
How can it be both an integral part of the CPU and board-specific?
Either it's under the direct control of the cpu or it's not. If it
is, that's cpu-specific and handled by the regular cacheops. If it's
not, that's board-specific and is called from a hook into something
which the machine detection has set up.
> I favor the idea where the cache takes care of external cache dynamically,
> based on some parameters set up by board detection routine.
So we end up filling the cache routines with tests for board-specific
stuff? No way. The cache routines should be dependent ONLY on the
CPU - two completely different boards with radically different designs
should be able to use the exact same foo-cache.c if they have the same
CPU. If it's board-specific we can put generic hooks in but testing
for various boards in the cacheops is too expensive and too ugly.
--
Keith M Wesolowski <wesolows@foobazco.org> http://foobazco.org/~wesolows
------(( Project Foobazco Coordinator and Network Administrator ))------
"I should have crushed his marketing-addled skull with a fucking bat."
next prev parent reply other threads:[~2001-04-05 21:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-02 6:52 RFC: Cleanup/detection patch Keith M Wesolowski
2001-04-04 2:43 ` Jun Sun
2001-04-04 3:30 ` Keith M Wesolowski
2001-04-04 17:54 ` Jun Sun
2001-04-05 7:46 ` Keith M Wesolowski
2001-04-05 20:29 ` Jun Sun
2001-04-05 21:03 ` Keith M Wesolowski [this message]
2001-04-05 21:53 ` Jun Sun
2001-04-09 6:40 ` Geert Uytterhoeven
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=20010405140338.A1508@foobazco.org \
--to=wesolows@foobazco.org \
--cc=jsun@mvista.com \
--cc=linux-mips@oss.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