linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] Warp speed building
Date: Wed, 17 Jun 2009 08:47:07 +0200	[thread overview]
Message-ID: <4A38916B.90509@web.de> (raw)
In-Reply-To: <43e72e890906161307w1441e26dnec48bbb1f88c38fd@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1905 bytes --]

Luis R. Rodriguez wrote:
> On Tue, Jun 16, 2009 at 11:39 AM, Hauke Mehrtens<hauke@hauke-m.de> wrote:
>> Jan Kiszka wrote:
>>> Including config.mk again when kbuild called into the top level Makefile
>>> slowed down the build process awfully. The reason for this were all the
>>> dynamic, shell-based variable evaluations that were called over and over
>>> again. Fortunately, including config.mk only in the outer Makefile run
>>> appears to be enough. So let's remove this warp speed blocker.
>>>
>>> Signed-off-by: Jan Kiszka <jan.kiszka@web.de>
>>> ---
>>>  Makefile |    2 --
>>>  1 files changed, 0 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/Makefile b/Makefile
>>> index 0ab7d27..49a786a 100644
>>> --- a/Makefile
>>> +++ b/Makefile
>>> @@ -13,8 +13,6 @@ OLD_IWL=$(shell $(MODPROBE) -l iwl4965)
>>>
>>>  ifneq ($(KERNELRELEASE),)
>>>
>>> -include $(M)/$(COMPAT_CONFIG)
>>> -
>>>  NOSTDINC_FLAGS := -I$(M)/include/ -include $(M)/include/net/compat.h $(CFLAGS)
>>>
>>>  obj-y := net/wireless/ net/mac80211/ net/rfkill/
>> Hi Jan,
>>
>> I have tested this patch and it reduced the build time for me from 3:30
>> to 2:40 minutes on a dual core system. I can not see any changes, expect
>> the reduced build time on my system. The resulting modules are still the
>> same.
> 
> Reason for including the config.mk is if your current kernel config
> differs the makefiles won't pick up the new stuff.

I had tested this before, and it did work nicely. To my understanding,
the 'export' in config.mk should carry all the defines into the nested
make calls.

Moreover, I'm surprised about this minimal reduction in Hauke's test.
Already running 'make clean' (no -j used for this) goes down from

    real    3m12.564s
    user    3m2.675s
    sys     0m8.461s

to

    real    0m20.670s
    user    0m17.337s
    sys     0m2.656s

here.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

      reply	other threads:[~2009-06-17  6:47 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
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 [this message]

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=4A38916B.90509@web.de \
    --to=jan.kiszka@web.de \
    --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).