From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: William Lee Irwin III <wli@holomorphy.com>,
Hugh Dickins <hugh@veritas.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: slub-i386-support.patch
Date: Thu, 10 May 2007 14:22:11 -0700 [thread overview]
Message-ID: <46438D03.8030100@goop.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0705101333420.11826@schroedinger.engr.sgi.com>
Christoph Lameter wrote:
>> This is wrong; pgd's are smaller than PAGE_SIZE on PAE. Burning lowmem
>> like this is very, very bad for such systems. pmd_cache is rather
>> trivial to convert to quicklists, since all it does is zero pages. I
>> still don't approve of even the !SHARED_KERNEL_PMD case using PAGE_SIZE
>> -sized pgd's. Xen should really be fixed to avoid requiring guests to
>> have recursive pagetables or whatever it's doing.
>>
>
> But the Xen guys need the full sized pgd?
>
Yes, Xen needs a page-sized PGD. There are two reasons:
1. Xen inherently needs a whole page for the pgd, because it
classifies pages by type, and the pgd is a pagetable-typed page.
2. When the kernel mappings are not being shared between processes,
as in non-PAE or PAE with !SHARED_KERNEL_PMD, it maintains a
pgd_list linked though the index field in the page structure's
index field. For this to work, you can't have more than one pgd
per page. The pgd_list is needed to sync the vmalloc mappings
across all the pagetables.
Xen needs to set !SHARED_KERNEL_PMD for PAE when running a 32-bit kernel
under a 32-bit hypervisor; when running under a 64-bit hypervisor,
there's no need to steal any guest address space for the hypervisor. (I
haven't implemented this on the Linux side yet.)
J
next prev parent reply other threads:[~2007-05-10 21:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 20:03 slub-i386-support.patch Hugh Dickins
2007-05-10 20:17 ` slub-i386-support.patch Andrew Morton
2007-05-10 20:31 ` slub-i386-support.patch Christoph Lameter
2007-05-10 20:50 ` slub-i386-support.patch David Miller
2007-05-10 20:31 ` slub-i386-support.patch William Lee Irwin III
2007-05-10 20:35 ` slub-i386-support.patch Christoph Lameter
2007-05-10 21:09 ` slub-i386-support.patch William Lee Irwin III
2007-05-10 21:28 ` slub-i386-support.patch Jeremy Fitzhardinge
2007-05-10 23:35 ` slub-i386-support.patch William Lee Irwin III
2007-05-10 21:22 ` Jeremy Fitzhardinge [this message]
2007-05-10 23:14 ` slub-i386-support.patch Hugh Dickins
2007-05-11 0:07 ` slub-i386-support.patch William Lee Irwin III
2007-05-11 1:08 ` slub-i386-support.patch William Lee Irwin III
2007-05-11 5:09 ` slub-i386-support.patch Christoph Lameter
2007-05-11 7:43 ` slub-i386-support.patch William Lee Irwin III
2007-05-11 1:42 ` slub-i386-support.patch William Lee Irwin III
2007-05-11 8:29 ` slub-i386-support.patch Andi Kleen
2007-05-11 7:42 ` slub-i386-support.patch Andrew Morton
2007-05-11 7:54 ` slub-i386-support.patch William Lee Irwin III
2007-05-11 16:15 ` slub-i386-support.patch Christoph Lameter
2007-05-11 20:47 ` slub-i386-support.patch William Lee Irwin III
2007-05-11 9:27 ` slub-i386-support.patch Hugh Dickins
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=46438D03.8030100@goop.org \
--to=jeremy@goop.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=wli@holomorphy.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