linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Paul Mackerras <paulus@samba.org>
Cc: David Gibson <david@gibson.dropbear.id.au>,
	linuxppc-embedded@lists.linuxppc.org,
	Tom Rini <trini@kernel.crashing.org>
Subject: Re: Do we need tlbsx at finish_tlb_load?
Date: Tue, 04 Jun 2002 13:49:36 -0400	[thread overview]
Message-ID: <3CFCFDB0.9010304@embeddededge.com> (raw)
In-Reply-To: 15612.47115.300768.766742@argo.ozlabs.ibm.com


Paul Mackerras wrote:


> If the PTE isn't valid (i.e. the _PAGE_PRESENT bit is 0) we don't put
> it into the TLB.

OK, so remove the tlbsx..........The tlb handler doesn't look like the
one I originally wrote, so whoever made the changes should have understood
and changed everything.  I'm just explaining why it was there in the first
place, maybe it isn't needed anymore.

IMHO, a tlb miss handler design should simply emulate a hardware implementation,
and fetch the PTE entries into the TLB cache as quickly and efficiently as
possible.  You are typically loading valid, ready to use PTEs in a much higher
proportion to invalid ones, and I don't like the normal fast path cluttered
by the overhead of checking the special cases that require more work.


Thanks.


	-- Dan


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

  reply	other threads:[~2002-06-04 17:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-30  8:04 Do we need tlbsx at finish_tlb_load? David Gibson
2002-06-03  2:43 ` David Gibson
2002-06-04  0:19   ` Dan Malek
2002-06-04  3:48     ` David Gibson
2002-06-04 12:52     ` Paul Mackerras
2002-06-04 17:49       ` Dan Malek [this message]
2002-06-06  2:04         ` Paul Mackerras
2002-06-06  5:06           ` Dan Malek

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=3CFCFDB0.9010304@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=paulus@samba.org \
    --cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).