All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Yuhong Bao <yuhongbao_386@hotmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: Ubuntu 32-bit, 32-bit PAE, 64-bit Kernel Benchmarks
Date: Fri, 15 Jan 2010 17:49:06 -0800	[thread overview]
Message-ID: <4B511B12.6010208@zytor.com> (raw)
In-Reply-To: <SNT125-W41CEF6892DBE0B1FD99B4AC3780@phx.gbl>

On 12/30/2009 05:29 PM, Yuhong Bao wrote:
> 
> Given that Linus was once talking about the performance penalties of PAE and HIGHMEM64G, perhaps you'd find these benchmarks done by Phoronix of interest:
> http://www.phoronix.com/scan.php?page=article&item=ubuntu_32_pae
> 

The big difference isn't between HIGHMEM4G (no PAE) and HIGHMEM64G
(PAE), it's between HIGHMEM and !HIGHMEM.  That cutoff is ~892 MB for a
stock 32-bit kernel.

	-hpa

  parent reply	other threads:[~2010-01-16  1:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-31  1:29 Ubuntu 32-bit, 32-bit PAE, 64-bit Kernel Benchmarks Yuhong Bao
2009-12-31  2:49 ` Bill Davidsen
2009-12-31  8:21   ` Boaz Harrosh
2009-12-31 16:32     ` Bill Davidsen
2009-12-31 17:49       ` Pedro Ribeiro
2009-12-31 18:39 ` Linus Torvalds
2010-01-03  3:39   ` Yuhong Bao
2010-01-16  0:48   ` Yuhong Bao
2010-01-16  1:49 ` H. Peter Anvin [this message]
2010-01-16  2:06   ` Yuhong Bao
2010-01-16  3:47     ` Linus Torvalds
2010-01-16  4:32       ` yuhongbao_386
2010-01-16  4:53     ` H. Peter Anvin
2010-01-16  6:17       ` yuhongbao_386
2010-01-16 17:59       ` Bill Davidsen
2010-01-17  9:26         ` matthieu castet
2010-01-31 17:03       ` Robert Hancock
2010-01-16 12:33   ` Sitsofe Wheeler
2010-01-16 12:57     ` Robert P. J. Day
2010-01-16 17:11       ` H. Peter Anvin
2010-03-01  1:31   ` Yuhong Bao
2010-03-01  1:38   ` Yuhong Bao
2010-01-16  8:46 ` Geert Uytterhoeven

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=4B511B12.6010208@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=torvalds@linux-foundation.org \
    --cc=yuhongbao_386@hotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.