Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Craig Hada <chada@cup.hp.com>
To: hppa-linux@thepuffingroup.com
Subject: Re: [hppa-linux] Qn on PA-RISC Page tables and TLB
Date: Thu, 25 Mar 1999 12:31:37 -0800	[thread overview]
Message-ID: <199903252031.MAA27090@psalpha2.cup.hp.com> (raw)
In-Reply-To: Your message of "Wed, 24 Mar 1999 23:10:36 PST." <Pine.LNX.3.96.990324225944.502B-100000@quark.ix.netcom.com>

> 
> 
> PA-RISC Arch 1.1 book says:
> On page 3-14:
> 
> 	Exact form of these tables is s/w convention. 
> 
> Q.	If the format is software convention, does that mean
> 	the fields within TLB slots are not defined by Hardware ?
> 	Though  the book does seem to indicate what fields are needed
> 	in a pdir entry. Without knowing exact positions of various
> 	fields how would TLB entries be updated from pdir entries in
> 	memory ?
> 

In the absense of a harware TLB walker, the page directory format can be
structured by software to fit its needs. However, the TLB miss handler
must reformat the bits to fit the format of the TLB insert instructions.
To get maximum performace from the system, the TLB miss handlers must be
made very efficient. The format of the page directory entry in the PA-RISC 
Arch 1.1 book minimizes the work of the TLB miss handlers by aligning the
fields to match the format of the TLB insert instructions.

In order to enable the hardware TLB walker, the format of the page directory
must match the format from PA-RISC Arch 1.1 book. In addition, the memory
for the page directory must be equivalently mapped, power of two size aligned
(ie a page directory 1 MB in size must start on a 1 MB boundary), and 
contiguous. 

> 	Other interesting point to note is that PA-RISC does not
> 	define how many entries in the table etc. Very much unlike
> 	x86.
> 
> -pkd

The number of entries in the page directory are a function of the amount of 
memory and the amount of memory mapped I/O in the box. Since the hash
function is not perfect, the size of page directory can be tuned to meet
the system requirements.

-Craig
> 	
> 
> 
> 
> 
> -------------------------------------------------------------------------
> To unsubscribe: send e-mail to hppa-linux-request@thepuffingroup.com with
> `unsubscribe' as the subject.

  parent reply	other threads:[~1999-03-25 20:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-25  7:10 [hppa-linux] Qn on PA-RISC Page tables and TLB Kumar
1999-03-25 17:18 ` Grant Grundler
1999-03-25 20:31 ` Craig Hada [this message]
1999-03-28 20:37   ` Kumar
1999-03-28 22:52     ` Michael Shalayeff
1999-03-29 16:01     ` Craig Hada
  -- strict thread matches above, loose matches on Subject: below --
1999-03-25 15:59 Bjorn Helgaas

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=199903252031.MAA27090@psalpha2.cup.hp.com \
    --to=chada@cup.hp.com \
    --cc=hppa-linux@thepuffingroup.com \
    /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