public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: Christoph Lameter <clameter@sgi.com>,
	Dave Hansen <haveblue@us.ibm.com>, Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Mel Gorman <mel@csn.ul.ie>
Subject: Re: [PATCH] add a clear_pages function to clear pages of higher order
Date: 18 Mar 2005 11:12:00 +0100
Date: Fri, 18 Mar 2005 11:12:00 +0100	[thread overview]
Message-ID: <20050318101200.GA79386@muc.de> (raw)
In-Reply-To: <200503111008.12134.vda@port.imtp.ilyichevsk.odessa.ua>

> Andi Kleen (iirc) says that non-temporal stores seem to be
> big win in microbenchmarks (and I second that), but they are
> a net loss when we are going to use zeroed page just after
> zeroing. He recommends avoid using non-temporal stores

The rule of thumb is to only use non temporal stores when your
data set is bigger than the L2/L3 caches of the CPU. This means >1MB.
The kernel normally never works on data sets that big.

For Christophers new background cleaner daemon it may be worth it 
when the queue is a LILO. This means it is likely there is a relatively
long time between the clearing operation and a workload using it.
But even then it is a very close call and would need clear benchmark 
numbers in macrobenchmarks.

-Andi


      parent reply	other threads:[~2005-03-18 10:12 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-10 20:35 [PATCH] add a clear_pages function to clear pages of higher order Christoph Lameter
2005-03-10 21:38 ` Dave Hansen
2005-03-10 22:46   ` Christoph Lameter
2005-03-11  1:03   ` Christoph Lameter
2005-03-11  8:08     ` Denis Vlasenko
2005-03-17  1:33       ` Christoph Lameter
2005-03-18  9:54         ` Denis Vlasenko
2005-03-18 15:00           ` Christoph Lameter
2005-03-18 19:28             ` Andi Kleen
2005-03-18 20:19               ` Christoph Lameter
2005-03-21 15:30               ` Denis Vlasenko
2005-03-24 18:34               ` David Mosberger
2005-03-24 18:41                 ` Christoph Lameter
2005-03-24 19:03                   ` David S. Miller
2005-03-24 22:49                     ` Christoph Lameter
2005-03-24 23:13                       ` David S. Miller
2005-03-25  2:29                       ` David S. Miller
2005-03-25  2:43                         ` Christoph Lameter
2005-03-27 17:12                 ` Andi Kleen
2005-03-27 18:23                   ` David S. Miller
2005-03-29  1:58                   ` Christoph Lameter
2005-04-06  0:15                 ` Christoph Lameter
2005-04-06  0:23                   ` David Mosberger
2005-04-06  0:33                     ` Christoph Lameter
2005-04-06  4:48                       ` David Mosberger
2005-04-06  5:15                         ` Gerrit Huizenga
2005-04-06 16:03                           ` Grant Grundler
2005-03-18 10:12       ` Andi Kleen [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=20050318101200.GA79386@muc.de \
    --to=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mel@csn.ul.ie \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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