From: Michael Buesch <mb@bu3sch.de>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Jan Kiszka <jan.kiszka@web.de>, linux-wireless@vger.kernel.org
Subject: Re: compat-wireless: ridiculous build speed
Date: Thu, 11 Jun 2009 23:05:33 +0200 [thread overview]
Message-ID: <200906112305.33675.mb@bu3sch.de> (raw)
In-Reply-To: <43e72e890906111148w1c242bd1qf97cb668a98f883e@mail.gmail.com>
On Thursday 11 June 2009 20:48:13 Luis R. Rodriguez wrote:
> On Thu, Jun 11, 2009 at 2:29 AM, Jan Kiszka<jan.kiszka@web.de> wrote:
> > Hi,
> >
> > while watching compat-wireless-2009-06-11 doing baby-steps building all
> > its modules, I wonder what slows this down so horribly. No other
> > external module build package I know is that slow (I would say *at
> > least* one order of magnitude slower than normal). Is this really required?
> >
> > [ Hurray, it's finished! ]
>
> I think the many depmod -ae are the culprit. This is in place to
> account for all the crap of madwifi which may be present or older
> drivers which have been renamed.
>
> This could be improved. Patches are welcomed.
>
> Ps. Try building with make -j 2, etc.
-j does not help. It will hardly build in parallel then. There's something
that serializes most of it (implicitly).
--
Greetings, Michael.
next prev parent reply other threads:[~2009-06-11 21:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 9:29 compat-wireless: ridiculous build speed Jan Kiszka
2009-06-11 18:48 ` Luis R. Rodriguez
2009-06-11 21:05 ` Michael Buesch [this message]
2009-06-11 21:10 ` Luis R. Rodriguez
2009-06-11 21:14 ` Michael Buesch
2009-06-11 21:39 ` Gábor Stefanik
2009-06-11 21:43 ` Luis R. Rodriguez
2009-06-13 8:53 ` [PATCH] Warp speed building Jan Kiszka
2009-06-16 18:39 ` Hauke Mehrtens
2009-06-16 20:07 ` Luis R. Rodriguez
2009-06-17 6:47 ` Jan Kiszka
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=200906112305.33675.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=jan.kiszka@web.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.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 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).