linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Christoph Lameter <clameter@sgi.com>
Cc: Paul Mackerras <paulus@samba.org>, Rik van Riel <riel@redhat.com>,
	Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
	David Woodhouse <dwmw2@infradead.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: A scrub daemon (prezeroing)
Date: Fri, 04 Feb 2005 17:43:23 +1100	[thread overview]
Message-ID: <1107499403.5461.32.camel@npiggin-nld.site> (raw)
In-Reply-To: <Pine.LNX.4.58.0502032220430.28851@schroedinger.engr.sgi.com>

On Thu, 2005-02-03 at 22:26 -0800, Christoph Lameter wrote:
> On Fri, 4 Feb 2005, Paul Mackerras wrote:
> 
> > As has my scepticism about pre-zeroing actually providing any benefit
> > on ppc64.  Nevertheless, the only definitive answer is to actually
> > measure the performance both ways.
> 
> Of course. The optimization depends on the type of load. If you use a
> benchmark that writes to all pages in a page then you will see no benefit
> at all. For a kernel compile you will see a slight benefit. For processing
> of a sparse matrix (page tables are one example) a significant benefit can
> be obtained.

If you have got to the stage of doing "real world" tests, I'd be
interested to see results of tests that best highlight the improvements.

I imagine many general purpose server things wouldn't be helped much,
because they'll typically have little free memory, and will be
continually working and turning things over.

A kernel compile on a newly booted system? Well that is a valid test.
It is great that performance doesn't *decrease* in that case :P

Of course HPC things may be a different story. It would be good to
see your gross improvement on typical types of workloads that can best
leverage this - and not just initial ramp up phases while memory is
being faulted in, but the the full run time.

Thanks,
Nick



--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2005-02-04  6:43 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-21 20:29 Christoph Lameter
2005-01-27 12:15 ` David Woodhouse
2005-01-27 13:12   ` Robin Holt
2005-01-27 13:14     ` David Woodhouse
2005-01-27 17:02       ` Christoph Lameter
2005-02-08 11:31     ` Ralf Baechle
2005-02-02 15:32   ` Marcelo Tosatti
2005-02-02 19:05     ` Christoph Lameter
2005-02-02 16:31       ` Marcelo Tosatti
2005-02-02 21:31         ` Christoph Lameter
2005-02-02 21:39         ` David Woodhouse
2005-02-03  3:06         ` Rik van Riel
2005-02-03 23:39           ` Paul Mackerras
2005-02-04  0:59             ` Christoph Lameter
2005-02-04  5:30               ` Paul Mackerras
2005-02-04  6:26                 ` Christoph Lameter
2005-02-04  6:43                   ` Nick Piggin [this message]
2005-02-04  6:50                     ` Christoph Lameter
2005-02-04  9:20                   ` Paul Mackerras
2005-02-04  9:28                     ` Andi Kleen
2005-02-04 17:02                     ` Christoph Lameter
2005-02-04 22:25                       ` Paul Mackerras
2005-02-02 21:00     ` Maciej W. Rozycki
2005-02-02 21:33       ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2005-01-04 23:13 Prezeroing V3 [1/4]: Allow request for zeroed memory Christoph Lameter
2005-01-08 21:12 ` Hugh Dickins
2005-01-08 21:56   ` David S. Miller
2005-01-21 20:15     ` A scrub daemon (prezeroing) Christoph Lameter

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=1107499403.5461.32.camel@npiggin-nld.site \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=paulus@samba.org \
    --cc=riel@redhat.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