From: Johannes Berg <johannes@sipsolutions.net>
To: Sujith Manoharan <c_manoha@qca.qualcomm.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
Hauke Mehrtens <hauke@hauke-m.de>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 0/2] compat: fix extreme build slowdowns
Date: Fri, 30 Mar 2012 13:30:22 +0200 [thread overview]
Message-ID: <1333107022.3908.16.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20341.39041.645223.592030@gargle.gargle.HOWL>
On Fri, 2012-03-30 at 16:56 +0530, Sujith Manoharan wrote:
> Johannes Berg wrote:
> > Somehow exporting too many variables completely confuses the kernel's
> > Makefiles into trying to calculate the size of every file in a very slow
> > shell script ... this is causing EXTREME build slowdowns for me.
> >
> > These two patches fix it.
>
> Nice.
>
> Trying to build ath9k..
>
> Before:
>
> real 1m18.689s
> user 3m1.382s
> sys 0m6.833s
>
> After:
>
> real 0m42.091s
> user 1m30.024s
> sys 0m5.700s
Yeah, I also see about 50% build time now with everything in cache, if
the files it's sizing up aren't in cache then it can be much slower with
the old version.
johannes
next prev parent reply other threads:[~2012-03-30 11:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 11:10 [PATCH 0/2] compat: fix extreme build slowdowns Johannes Berg
2012-03-30 11:11 ` [PATCH 1/2] compat-wireless: include config.mk early Johannes Berg
2012-03-30 11:11 ` [PATCH 2/2] compat: explicitly export generated variables Johannes Berg
2012-03-30 20:30 ` Luis R. Rodriguez
2012-03-30 20:34 ` Johannes Berg
2012-03-30 20:38 ` Luis R. Rodriguez
2012-03-30 11:26 ` [PATCH 0/2] compat: fix extreme build slowdowns Sujith Manoharan
2012-03-30 11:30 ` Johannes Berg [this message]
2012-03-30 14:41 ` Richard Farina
2012-03-30 20:43 ` Luis R. Rodriguez
2012-03-30 21:24 ` Luis R. Rodriguez
2012-03-30 21:48 ` Luis R. Rodriguez
2012-03-31 9:24 ` Luis R. Rodriguez
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=1333107022.3908.16.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=c_manoha@qca.qualcomm.com \
--cc=hauke@hauke-m.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).