linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Tigran Aivazian <tigran@veritas.com>
Cc: Timur Tabi <ttabi@interactivesi.com>,
	Linux MM mailing list <linux-mm@kvack.org>,
	Linux Kernel Mailing list <linux-kernel@vger.kernel.org>
Subject: Re: How does the kernel map physical to virtual addresses?
Date: Mon, 28 Aug 2000 16:12:52 +0100	[thread overview]
Message-ID: <20000828161252.C1467@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0008281351470.1021-100000@saturn.homenet>; from tigran@veritas.com on Mon, Aug 28, 2000 at 01:56:34PM +0100

Hi,

On Mon, Aug 28, 2000 at 01:56:34PM +0100, Tigran Aivazian wrote:
> 
> it is interesting to observe that many questions that deal with _details_
> are answered quickly but questions related to fundamental concepts related
> to how Linux is designed, baffle all of us (since 0 people answered). So,
> is there really nobody in the whole world who can answer this? I would
> like to know the answer (about global kernel memory layout - i.e. what
> goes into PSE pages and what goes into normal ones, and how does PAE mode
> change the picture?) myself...

If PSE is available, it is used to map the bits of the kernel's
VA which permanently maps all of physical memory.  As a result, those
pages cannot necessarily be looked up via a normal page table walk.
Anything dynamically mapped --- ie. high pages (if using PAE), or
vmalloc/ioremap pages --- is mapped using normal 4k ptes.  

mem_map[] is completely unaffected by the use of PSE, and continues to
keep one entry per 4k physical page regardless of how the page tables
have been constructed.

--Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

  reply	other threads:[~2000-08-28 15:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20000825233748Z130198-15329+2857@vger.kernel.org>
2000-08-28 12:56 ` Tigran Aivazian
2000-08-28 15:12   ` Stephen C. Tweedie [this message]
2000-08-25 23:26 Timur Tabi
2000-08-28 12:41 ` Roman Zippel

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=20000828161252.C1467@redhat.com \
    --to=sct@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=tigran@veritas.com \
    --cc=ttabi@interactivesi.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