linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Derek Foreman <manmower@signalmarketing.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Adam Kropelin <akropel1@rochester.rr.com>, linux-kernel@vger.kernel.org
Subject: Re: Parallel build not working since -test6?
Date: Fri, 28 Nov 2003 20:47:54 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0311282039170.23104@uberdeity> (raw)
In-Reply-To: <200311282126.59634.sam@ravnborg.org>

On Fri, 28 Nov 2003, Sam Ravnborg wrote:

> On Thursday 27 November 2003 00:27, Adam Kropelin wrote:
> > Lately I've noticed my kernel compilations taking longer than usual.
> > Tonight I finally realized the cause... Parallel building (i.e. make -jN)
> > is no longer working for me. I traced it back and the last kernel it worked
> > in was -test5. It ceased working in -test6.
> It works for me, and for sure it works for most others. Otherwise I would
> have seen lot of complaints like yours.
> I recall one similar post, and the person in question used a homegrown
> script that caused the problems.

Well, this explains why 2.6.x builds so much slower here than it did a few
kernels ago.

make -j3 improves things.  but currently, make -j2 doesn't use both my
cpus.

no scripts, just make -j2 bzImage

  parent reply	other threads:[~2003-11-29  2:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-26 23:27 Parallel build not working since -test6? Adam Kropelin
2003-11-28 20:26 ` Sam Ravnborg
2003-11-29  1:47   ` Adam Kropelin
2003-11-29  2:47   ` Derek Foreman [this message]
2003-11-29  3:40     ` Adam Kropelin

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=Pine.LNX.4.58.0311282039170.23104@uberdeity \
    --to=manmower@signalmarketing.com \
    --cc=akropel1@rochester.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).