All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Anton Blanchard <anton@linuxcare.com.au>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org,
	Stephen Tweedie <sct@redhat.com>
Subject: Re: [PATCH]: Only one memory zone for sparc64
Date: Fri, 16 Mar 2001 12:16:54 +0000	[thread overview]
Message-ID: <20010316121654.C1771@redhat.com> (raw)
In-Reply-To: <20010315191352.D1598@linuxcare.com>
In-Reply-To: <20010315191352.D1598@linuxcare.com>; from anton@linuxcare.com.au on Thu, Mar 15, 2001 at 07:13:52PM +1100

Hi,

On Thu, Mar 15, 2001 at 07:13:52PM +1100, Anton Blanchard wrote:
> 
> On sparc64 we dont care about the different memory zones and iterating
> through them all over the place only serves to waste CPU. I suspect this
> would be the case with some other architectures but for the moment I
> have just enabled it for sparc64.
> 
> With this patch I get close to a 1% improvement in dbench on the dual
> ultra60.

I'd be surprised if dbench was anything other than disk-bound on most
systems.  On any of my machines, the standard error of a single dbench
run is *way* larger than 1%, and I'd expect to have to run the
benchmark a dozen times to get a confidence interval small enough to
detect a 1% performance change: are your runs repeatable enough to be
this sensitive to the effect of the allocator?

Cheers,
 Stephen

  parent reply	other threads:[~2001-03-16 20:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-15  8:13 [PATCH]: Only one memory zone for sparc64 Anton Blanchard
2001-03-15 12:36 ` Rik van Riel
2001-03-16 12:16 ` Stephen C. Tweedie [this message]
2001-03-17  2:45   ` Anton Blanchard

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=20010316121654.C1771@redhat.com \
    --to=sct@redhat.com \
    --cc=anton@linuxcare.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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.