From: Jun Sun <jsun@mvista.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: "Kevin D. Kissell" <kevink@mips.com>,
Hartvig Ekner <hartvig@ekner.info>,
Linux MIPS mailing list <linux-mips@linux-mips.org>,
jsun@mvista.com
Subject: Re: MIPS32 cache functions now using c-r4k?
Date: Wed, 16 Apr 2003 09:51:35 -0700 [thread overview]
Message-ID: <20030416095135.U1642@mvista.com> (raw)
In-Reply-To: <20030416160818.E9170@linux-mips.org>; from ralf@linux-mips.org on Wed, Apr 16, 2003 at 04:08:19PM +0200
On Wed, Apr 16, 2003 at 04:08:19PM +0200, Ralf Baechle wrote:
> On Wed, Apr 16, 2003 at 02:59:30PM +0200, Kevin D. Kissell wrote:
>
> > The whole point of creating the generic MIPS32 MMU and cache
> > routines was to have something that would run on both 32-bit and
> > 64-bit processors. Who decided to throw them away and abandon
> > support for 32-bit-only CPUs other than the R3000, and why?
>
> Nobody did dump support for 32-bit only processors.
>
> The read behind all this was in part that the pile of c-*.c files had
> turned into some sort of barbed wire fence. Code from c-r4k.c had been
> replicated several times - including hundreds (conservative estimate) of
> lines of dead code, plenty of bugs and lack of understanding how caches
> are working. At the same time that meant there was no way the old code
> could have supported all available processor configurations on some
> platforms.
>
It is really a Good Thing(tm) to have a more uniformed cache routine
and actually an overall performance gain. It makes the tree more maintainable
and that new abstraction enables us to accomodate any new wacky CPUs
if there dare to any. :)
This is a long overdue task. And the first derailed c-* file really should
not be allowed at the first place. :)
Jun
next prev parent reply other threads:[~2003-04-16 16:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 7:54 MIPS32 cache functions now using c-r4k? Hartvig Ekner
2003-04-16 12:59 ` Kevin D. Kissell
2003-04-16 13:19 ` Maciej W. Rozycki
2003-04-16 14:08 ` Ralf Baechle
2003-04-16 16:51 ` Jun Sun [this message]
2003-04-16 13:17 ` Maciej W. Rozycki
2003-04-16 14:59 ` Ralf Baechle
2003-04-16 17:51 ` Hartvig Ekner
2003-04-16 19:19 ` 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=20030416095135.U1642@mvista.com \
--to=jsun@mvista.com \
--cc=hartvig@ekner.info \
--cc=kevink@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
/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