Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "William J. Earl" <wje@fir.engr.sgi.com>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: ralf@uni-koblenz.de, linux-mips@fnet.fr,
	linux-mips@vger.rutgers.edu, linux@cthulhu.engr.sgi.com
Subject: Re: Tags are dead alias Milo is dead part II
Date: Thu, 8 Oct 1998 13:30:36 -0700	[thread overview]
Message-ID: <199810082030.NAA04597@fir.engr.sgi.com> (raw)
In-Reply-To: <19981008215834.51243@alpha.franken.de>

Thomas Bogendoerfer writes:
 > On Thu, Oct 08, 1998 at 05:03:35PM +0200, ralf@uni-koblenz.de wrote:
 > > Applied to the G364 drivers (which as of now is still MIPS specific anyway)
 > > this means that we'll avoid TLB trashing in the case of scrolling and have
 > > the full TLB available for userland.
 > 
 > I don't believe this will buy us anything. When we add a temporary TLB we need
 > do clear one TLB, which might be used by the userland. So we end up loading
 > our wired entry, killing it, and later the user process has to reload the 
 > TLB again. This way we force TLB trashing, with one wired entry more we
 > _might_ get a little bit more TLB trashing.
 > 
 > As you might know, I'm using three wired entries for the Magnum, and I don't 
 > think doing the same trick for the other entries is a real good idea. When 
 > we make them temporary, we have to mess with TLBs on every interrupt.

     You could do what IRIX does in some cases, which is to save and restore
the TLB entry you replace.  Beware of doing this, however, if your code could
take a page fault.

      reply	other threads:[~1998-10-08 20:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <19981007002547.44731@alpha.franken.de>
1998-10-08 15:03 ` Tags are dead alias Milo is dead part II ralf
1998-10-08 19:58   ` Thomas Bogendoerfer
1998-10-08 20:30     ` William J. Earl [this message]

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=199810082030.NAA04597@fir.engr.sgi.com \
    --to=wje@fir.engr.sgi.com \
    --cc=linux-mips@fnet.fr \
    --cc=linux-mips@vger.rutgers.edu \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=ralf@uni-koblenz.de \
    --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