public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Park <opengeometry@yahoo.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: Dual Athlon MP 1900+ on MSI K7D Master-L
Date: Fri, 19 Jul 2002 01:00:06 -0400	[thread overview]
Message-ID: <20020719050006.GB3590@node1.opengeometry.net> (raw)
In-Reply-To: <200207182114.30806.kelledin+LKML@skarpsey.dyndns.org>

On Thu, Jul 18, 2002 at 09:14:30PM -0500, Kelledin wrote:
> On Thursday 18 July 2002 08:31 pm, Dieter N?tzel wrote:
> > Alan, were should I put the "-j2/-j3" make flag for the kernel
> > compilation? /usr/src/linux/Documentation/smp.txt is way
> > outdated ;-(
...
> In general, I find it best to set the number of jobs to the 
> number of CPUs _plus 1_--i.e. for single CPU, use make -j2, and 
> for dual CPUs, use make -j3.  Going for that "plus 1" makes most 
> builds just a smidgen faster.  For me, on my dual PPro box, the 
> process would be something like:
> 
> make menuconfig
> make -j3 MAKE="make -j3" dep clean bzImage modules

I usually have better luck if I use only one target per 'make':
    make menuconfig
    make -j3 dep
    make clean
    make -j3 bzlilo
    make -j3 modules
    make -j3 modules_install
Especially, 'modules' and 'modules_install' must be done separately.

-- 
William Park, Open Geometry Consulting, <opengeometry@yahoo.ca>
8-CPU Cluster, Hosting, NAS, Linux, LaTeX, python, vim, mutt, tin

  reply	other threads:[~2002-07-19  4:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-19  1:31 Dual Athlon MP 1900+ on MSI K7D Master-L Dieter Nützel
2002-07-19  2:14 ` Kelledin
2002-07-19  5:00   ` William Park [this message]
2002-07-25 13:03   ` Bill Davidsen

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=20020719050006.GB3590@node1.opengeometry.net \
    --to=opengeometry@yahoo.ca \
    --cc=linux-kernel@vger.kernel.org \
    /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