public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Cole <elenstev@mesatop.com>
To: Mike Galbraith <mikeg@wen-online.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: UP 2.2.18 makes kernels 3% faster than UP 2.4.0-test12
Date: Mon, 11 Dec 2000 22:17:36 -0700	[thread overview]
Message-ID: <00121122173600.03488@localhost.localdomain> (raw)
In-Reply-To: <Pine.Linu.4.10.10012120529110.970-100000@mikeg.weiden.de>
In-Reply-To: <Pine.Linu.4.10.10012120529110.970-100000@mikeg.weiden.de>

On Mon, 11 Dec 2000, Mike Galbraith wrote:
> On Mon, 11 Dec 2000, Steven Cole wrote:
> > I have a SMP (dual P-III 733Mhz) machine at work, but it will be
> > unavailable for testing for a few more days.  I suspect that 2.4.0-test12
> > will do better than 2.2.18 with 2 CPUs.  I'll know in a few days.
[snip]
>
> I think it's better with -j.  Do it with -jN where N is small enough
> to keep the box away from swap, and then repeat with N large enough to
> swap modestly (not too heavily or you're only testing disk MTBF:).

I've always used make -j2 bzImage for my two processor machine. 
I like being able to build kernels in a little over two minutes. 

Simple question here, and risking displaying great ignorance:
Does it make sense to use make -jN where N is much greater than the 
number of CPUs?  

Steven
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-12  5:47 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-10 15:31 UP 2.2.18 makes kernels 3% faster than UP 2.4.0-test12 Steven Cole
2000-12-10 19:52 ` Aaron Tiensivu
2000-12-11 23:02   ` Steven Cole
2000-12-12  4:40     ` Mike Galbraith
2000-12-12  5:17       ` Steven Cole [this message]
2000-12-12  5:20         ` Mike Galbraith
2000-12-12 11:01         ` Helge Hafting
2000-12-12 10:27     ` Rik van Riel
2000-12-12 14:15       ` Mike Galbraith
  -- strict thread matches above, loose matches on Subject: below --
2000-12-10 20:36 Steven Cole
2000-12-11 18:16 ` John Fremlin
2000-12-11 18:38   ` Rik van Riel
2000-12-11 18:46     ` Alan Cox
2000-12-11 19:50       ` Zdenek Kabelac
2000-12-11 20:15       ` Arjan van de Ven
2000-12-11 20:23       ` Rik van Riel
2000-12-11 22:03       ` Gerhard Mack
2000-12-11 22:06         ` Alan Cox
2000-12-13  9:44           ` Rogier Wolff
2000-12-14 13:08             ` Russell King
2000-12-16  0:40               ` george anzinger
2000-12-12 14:49         ` Steven Cole
2000-12-12 18:18       ` Steven Cole
2000-12-12 18:40         ` Linus Torvalds
2000-12-12 20:19           ` Steven Cole
2000-12-12 20:38             ` Linus Torvalds
2000-12-12 22:09               ` Steven Cole
2000-12-11 22:12     ` Gabor Lenart

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=00121122173600.03488@localhost.localdomain \
    --to=elenstev@mesatop.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikeg@wen-online.de \
    /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