From: "H. Peter Anvin" <hpa@zytor.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Jeremy Fitzhardinge <jeremy@goop.org>, Andi Kleen <ak@suse.de>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Why preallocate pmd in x86 32-bit PAE?
Date: Thu, 15 Nov 2007 16:41:16 -0800 [thread overview]
Message-ID: <473CE72C.4060209@zytor.com> (raw)
In-Reply-To: <20071116004012.GE1806@holomorphy.com>
William Lee Irwin III wrote:
>
> There may be bigger fish to fry in terms of per-process overhead, if
> you're trying to cut that down. The trouble with trying to address
> some of those is that there is mutual antagonism between compactness
> and expansibility in the process address space layout, so you'll end
> up instantiating a lot more than you want barring some sort of provision
> for a compact address space layout. Pagetable sharing is a far more
> powerful resource scalability method, though it also needs cooperation
> in user address space layout to reap its gains.
>
> There are other overheads, of course, though they're more typically
> per-something besides processes.
>
I think Jeremy's question was due to trying to reduce the 32/64-bit
differences. Performance-wise, it might add a small amount to user
setup time (a typical 32-bit process will need all four, for the main
binary, libraries, stack and kernel, respectively) but it is probably
not significant (although I'd like to see numbers just in case).
-hpa
next prev parent reply other threads:[~2007-11-16 0:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 21:57 Why preallocate pmd in x86 32-bit PAE? Jeremy Fitzhardinge
2007-11-15 22:12 ` Linus Torvalds
2007-11-15 22:42 ` H. Peter Anvin
2007-11-16 0:40 ` William Lee Irwin III
2007-11-16 0:41 ` H. Peter Anvin [this message]
2007-11-16 11:16 ` Andi Kleen
2007-11-16 15:45 ` H. Peter Anvin
2007-11-16 15:53 ` Andi Kleen
2007-11-16 16:10 ` H. Peter Anvin
2007-11-16 17:12 ` Jeremy Fitzhardinge
2007-11-16 17:35 ` Linus Torvalds
2007-11-16 18:30 ` Jeremy Fitzhardinge
2007-11-16 19:14 ` Jeremy Fitzhardinge
2007-11-16 19:22 ` Linus Torvalds
2007-11-16 19:43 ` Jeremy Fitzhardinge
2007-11-16 17:45 ` H. Peter Anvin
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=473CE72C.4060209@zytor.com \
--to=hpa@zytor.com \
--cc=ak@suse.de \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=tglx@linutronix.de \
--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