All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: percpu-2.5.63-bk5-1 (properly generated)
Date: Sun, 2 Mar 2003 12:24:51 -0800	[thread overview]
Message-ID: <20030302202451.GJ1195@holomorphy.com> (raw)
In-Reply-To: <47970000.1046629477@[10.10.2.4]>

At some point in the past, I wrote:
>>> Tested, boots, and runs on NUMA-Q. Trims 6s of 41s off kernel compiles.

On Sun, Mar 02, 2003 at 10:24:37AM -0800, Martin J. Bligh wrote:
> Odd. I get nothing like that difference.
> Kernbench-2: (make -j N vmlinux, where N = 2 x num_cpus)
>                               Elapsed        User      System         CPU
>               2.5.63-mjb2       44.43      557.16       95.31     1467.83
>       2.5.63-mjb2-pernode       44.21      556.92       95.16     1474.33
> Kernbench-16: (make -j N vmlinux, where N = 16 x num_cpus)
>                               Elapsed        User      System         CPU
>               2.5.63-mjb2       45.39      560.26      117.25     1492.33
>       2.5.63-mjb2-pernode       44.78      560.24      112.20     1501.17
> No difference for make -j32, definite improvement in the systime for -j256.

Maybe your machine's running slow?
AFAIK the machines we're using are identical, and mine sees:

make -j bzImage > /dev/null  317.70s user 148.43s system 1295% cpu 35.984 total
(yes, this is 5 off of 41s, apparently 1s measurement variations are typical)

make -j36 bzImage > /dev/null  302.33s user 115.02s system 1284% cpu 32.492 total
make -j38 bzImage > /dev/null  302.52s user 117.06s system 1300% cpu 32.258 total
make -j40 bzImage > /dev/null  303.53s user 117.42s system 1305% cpu 32.251 total
make -j44 bzImage > /dev/null  304.02s user 122.14s system 1299% cpu 32.792 total

Check MTRR's etc.?


-- wli

  reply	other threads:[~2003-03-02 20:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-02 18:24 percpu-2.5.63-bk5-1 (properly generated) Martin J. Bligh
2003-03-02 20:24 ` William Lee Irwin III [this message]
2003-03-02 20:46   ` Martin J. Bligh
2003-03-02 21:06     ` William Lee Irwin III
2003-03-02 21:58       ` Martin J. Bligh
2003-03-02 22:10         ` William Lee Irwin III
2003-03-02 23:13           ` Martin J. Bligh
2003-03-02 23:42             ` William Lee Irwin III
2003-03-03  0:07               ` Martin J. Bligh
2003-03-03  1:43                 ` William Lee Irwin III
2003-03-03 17:40                   ` Martin J. Bligh
2003-03-03 22:51                     ` William Lee Irwin III
2003-03-03 23:30                       ` Martin J. Bligh
2003-03-04  0:14                         ` William Lee Irwin III
  -- strict thread matches above, loose matches on Subject: below --
2003-03-02 11:07 William Lee Irwin III
2003-03-02 13:15 ` William Lee Irwin III

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=20030302202451.GJ1195@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.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.