From: Douglas Anderson <dianders@chromium.org>
To: yamada.masahiro@socionext.com
Cc: groeck@chromium.org, sjg@chromium.org, briannorris@chromium.org,
mingo@kernel.org, Douglas Anderson <dianders@chromium.org>,
Matthias Kaehlcke <mka@chromium.org>,
Cao jin <caoj.fnst@cn.fujitsu.com>, Arnd Bergmann <arnd@arndb.de>,
James Hogan <jhogan@kernel.org>,
linux-kbuild@vger.kernel.org, Michal Marek <mmarek@suse.com>,
linux-kernel@vger.kernel.org,
Mark Charlebois <charlebm@gmail.com>
Subject: [PATCH v3 0/2] kbuild: Cache exploratory calls to the compiler
Date: Wed, 11 Oct 2017 09:19:22 -0700 [thread overview]
Message-ID: <20171011161924.11386-1-dianders@chromium.org> (raw)
This two-patch series attempts to speed incremental builds of the
kernel up by a bit. How much of a speedup you get depends a lot on
your environment, specifically the speed of your workstation and how
fast it takes to invoke the compiler.
In the Chrome OS build environment you get a really big win. For an
incremental build (via emerge) I measured a speedup from ~1 minute to
~35 seconds. ...but Chrome OS calls the compiler through a number of
wrapper scripts and also calls the kernel make at least twice for an
emerge (during compile stage and install stage), so it's a bit of a
worst case.
Perhaps a more realistic measure of the speedup others might see is
running "time make help > /dev/null" outside of the Chrome OS build
environment on my system. When I do this I see that it took more than
1.0 seconds before and less than 0.2 seconds after. So presumably
this has the ability to shave ~0.8 seconds off an incremental build
for most folks out there. While 0.8 seconds savings isn't huge, it
does make incremental builds feel a lot snappier.
Ingo Molnar also did some testing of this in his environment and found
that an incremental build of his subsystem sped up from ~.44 seconds
before to ~.15 seconds after. Clean builds also sped up by a marginal
amount. :)
Changes in v3:
- Rule to prevent make from trying to generate the cache
- Rule to clean .cache.mk
- No more doc changes
- Moved cache stuff below cc-cross-prefix
- Removed duplicate documentation of try-run (oops)
- Add Tested-by for Ingo and Guenter since v2 and v3 are very similar
Changes in v2:
- Abstract at a different level (like shell-cached) per Masahiro Yamada
- Include ld-version, which I missed the first time
Douglas Anderson (2):
kbuild: Add a cache for generated variables
kbuild: Cache a few more calls to the compiler
Makefile | 5 +--
scripts/Kbuild.include | 87 ++++++++++++++++++++++++++++++++++++++++++--------
2 files changed, 76 insertions(+), 16 deletions(-)
--
2.15.0.rc0.271.g36b669edcc-goog
next reply other threads:[~2017-10-11 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 16:19 Douglas Anderson [this message]
2017-10-11 16:19 ` [PATCH v3 1/2] kbuild: Add a cache for generated variables Douglas Anderson
2017-10-11 16:19 ` [PATCH v3 2/2] kbuild: Cache a few more calls to the compiler Douglas Anderson
2017-10-15 7:48 ` [PATCH v3 0/2] kbuild: Cache exploratory " Masahiro Yamada
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=20171011161924.11386-1-dianders@chromium.org \
--to=dianders@chromium.org \
--cc=arnd@arndb.de \
--cc=briannorris@chromium.org \
--cc=caoj.fnst@cn.fujitsu.com \
--cc=charlebm@gmail.com \
--cc=groeck@chromium.org \
--cc=jhogan@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mka@chromium.org \
--cc=mmarek@suse.com \
--cc=sjg@chromium.org \
--cc=yamada.masahiro@socionext.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).