public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: William Lee Irwin III <wli@holomorphy.com>,
	"Robert P. J. Day" <rpjday@mindspring.com>,
	Satyam Sharma <satyam.sharma@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ralf Baechle <ralf@linux-mips.org>
Subject: Re: why does the macro "ZERO_PAGE" take an argument?
Date: Tue, 12 Jun 2007 12:18:00 +1000	[thread overview]
Message-ID: <466E0258.2070407@yahoo.com.au> (raw)
In-Reply-To: <46687598.2040701@zytor.com>

H. Peter Anvin wrote:
> William Lee Irwin III wrote:
> 
>>Robert P. J. Day wrote:
>>
>>>>although it's not clear where in the source tree are the invocations
>>>>that would actually make a difference to a MIPS system, which is why
>>>>i've CC'ed ralf on this.  i'm sure he can clear this up. :-)
>>
>>On Thu, Jun 07, 2007 at 10:32:29AM -0700, H. Peter Anvin wrote:
>>
>>>x86 could also benefit from coloured zeropages.  In fact, I thought it
>>>already had them (K8 wants as many as 8.)
>>
>>How would one demonstrate the beneficial effect of such?
> 
> 
> Dean Gaudet at Transmeta did some benchmarking using SPEC.  If I recall
> his numbers correctly (this is from memory, mind you) on Transmeta
> Efficeon, which has 2-way virtual cache tagging with hardware recovery,
> zeropage coloring was a 1.5% performance improvement.

I'm surprised that the benchmark made such use of zero pages so as to
be worthwhile. I'm sitting on a patch which removes the zero page from
the page fault fastpath completely which I'd like to try out in -mm...

-- 
SUSE Labs, Novell Inc.

      parent reply	other threads:[~2007-06-12  2:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-07 11:17 why does the macro "ZERO_PAGE" take an argument? Robert P. J. Day
2007-06-07 11:29 ` Nick Piggin
2007-06-07 11:34   ` Robert P. J. Day
2007-06-07 11:39     ` Satyam Sharma
2007-06-07 11:53       ` Robert P. J. Day
2007-06-07 16:37         ` Ralf Baechle
2007-06-07 18:04           ` H. Peter Anvin
2007-06-07 17:32         ` H. Peter Anvin
2007-06-07 19:29           ` William Lee Irwin III
2007-06-07 21:16             ` H. Peter Anvin
2007-06-08  7:25               ` Robert P. J. Day
2007-06-09  0:49                 ` H. Peter Anvin
2007-06-12  2:18               ` Nick Piggin [this message]

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=466E0258.2070407@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=rpjday@mindspring.com \
    --cc=satyam.sharma@gmail.com \
    --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