linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: wung_y@263.net
Cc: linux-ppc <linuxppc-dev@lists.linuxppc.org>,
	linuxppc embedded mail list
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: What's MMU context?
Date: Wed, 27 Oct 1999 11:55:33 -0400	[thread overview]
Message-ID: <38172075.EC2839C2@netx4.com> (raw)
In-Reply-To: 3816E6FD.481FA27D@263.net


Wang Yong wrote:
> 
> as the source code of linuxPPC, there is a global variable named
> next_mmu_context which is increased by one at each time of create a new
> process. what does this mean and what is mmu context?


I intened to use it on the 8xx processors, as they have an address
space id that allows a TLB optimization so you don't have to
invalidate the entire TLB on context switches.  I assume the
MIPS folks use it as well, since that is where I first used
such an optimization (in an OS other than Linux).  Unfortunately,
the ratio of entries to ASIDs is wrong for my original MIPS-like
algorithm to work, and I never got around to writing something
new.

This was already part of the Linux/PPC port when I started the 8xx
work, and I don't know if other processors use it or if it was
just part of the generic port that was maintained.


	-- Dan

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~1999-10-27 15:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-27 11:50 What's MMU context? Wang Yong
1999-10-27 15:55 ` Dan Malek [this message]
1999-12-07  2:58   ` Debugging with thread(s) Claude Robitaille
1999-12-07 13:14     ` Frank McPherson
1999-12-12  0:00   ` Thread and malloc Claude Robitaille
  -- strict thread matches above, loose matches on Subject: below --
1999-10-28  4:42 What's MMU context? Wang Yong

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=38172075.EC2839C2@netx4.com \
    --to=dan@netx4.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=wung_y@263.net \
    /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;
as well as URLs for NNTP newsgroup(s).