From: Harald Koerfgen <harald.koerfgen@netcologne.de>
To: linux-mips@fnet.fr
Cc: linux@cthulhu.engr.sgi.com, Vladimir Roganov <roganov@niisi.msk.ru>
Subject: Re: get_mmu_context()
Date: Sun, 18 Oct 1998 21:53:18 +0200 (MEST) [thread overview]
Message-ID: <XFMail.981018215318.harald.koerfgen@netcologne.de> (raw)
In-Reply-To: <Pine.SV4.3.91.981016185136.876A-100000@mech.math.msu.su>
On 16-Oct-98 Gleb O. Rajko wrote:
> On Thu, 15 Oct 1998 ralf@uni-koblenz.de wrote:
>
>>
>> The performance hit will come into the game as soon as one tries to
>> build a generic kernel for both R3000 and R4000. The R3000 PID and the
>> R4000 ASID mechanism are slightly different and the simple approach
>> to fix that is to use global variables. Which affects both your version
>> and the current version.
> We are going to provide support for building generic kernels in the near
> future if somebody who holds r4k will help us and will try our patches
> on a r4k box. I think the best time to start is when r3k will be synced
> with the main branch. Perhaps, Harald may answer when it might occur.
Hmmm, I'm not shure about this. If we really want to support generic kernels,
that'll shurely needs some more work than a little patching in get_mmu_context.
Remember, Vladimir, we needed to make changes in extremely performance critical
parts of the kernel which Ralf propably won't like to have for the R4000 case. Most
of them are actually compiled conditionally.
To make those changes generic needs either a reasonable amount of hacking or
avoidable code duplication. In fact, if we really don't care about self modifying
code we should be able to remove some code duplication, for example in the fpu
stuff.
I'd personally prefer to have a few things sorted out before I check the R3000 stuff
in. What's common opinion on this?
---
Regards,
Harald
next prev parent reply other threads:[~1998-10-18 19:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-13 19:59 get_mmu_context() ralf
[not found] ` <Pine.LNX.3.96.981014144230.10483B-100000@mirkwood.dummy.home>
1998-10-14 23:49 ` get_mmu_context() ralf
[not found] ` <3625D799.7D923FA9@niisi.msk.ru>
1998-10-15 20:21 ` get_mmu_context() ralf
[not found] ` <Pine.SV4.3.91.981016185136.876A-100000@mech.math.msu.su>
1998-10-18 19:53 ` Harald Koerfgen [this message]
1998-10-19 10:18 ` get_mmu_context() ralf
1998-10-20 4:07 ` get_mmu_context() Warner Losh
1998-10-20 17:31 ` get_mmu_context() ralf
1998-10-20 23:36 ` get_mmu_context() Warner Losh
1998-10-21 19:31 ` get_mmu_context() Harald Koerfgen
1998-10-19 1:29 ` get_mmu_context() ralf
1998-10-16 22:44 ` get_mmu_context() ralf
-- strict thread matches above, loose matches on Subject: below --
1998-10-20 4:21 get_mmu_context() Ariel Faigon
1998-10-20 4:21 ` get_mmu_context() Ariel Faigon
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=XFMail.981018215318.harald.koerfgen@netcologne.de \
--to=harald.koerfgen@netcologne.de \
--cc=linux-mips@fnet.fr \
--cc=linux@cthulhu.engr.sgi.com \
--cc=roganov@niisi.msk.ru \
/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