From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: mingo@redhat.com
Subject: Tricks to speed up kernel builds
Date: Tue, 15 Sep 2009 11:22:37 +0300 [thread overview]
Message-ID: <4AAF4ECD.5010401@pardus.org.tr> (raw)
Hi,
I'd googled a lot about the $subject but couldn't find any detailed
guide about it. So, the followings are what I understand from what I've
found:
1. Build inside a tmpfs to avoid I/O bottlenecks,
2. Use ccache,
3. Switch governor to performance if supported,
4. Pass -j to gnu make to parallelize the build process,
5. Don't build debug symbols a.k.a set CONFIG_DEBUG_INFO=n
6. There are a bunch of sched patches in tip which apparently improves
things during kbuild
7. Distribute the work into the local network using icecream, distcc.
For the -j part, how many jobs should we pass to it? I've seen people
passing
- NR_of_cores+1
- NR_of_cores x 2 (I think that this is useful when there's 2 threads of
execution per core like HyperThreading?)
- 64, 128, etc. regardless of the number of cores (Is it really useful
regardless of the CPU)
The curious question is *what build times can you get* with your typical
systems using your speedup tricks (quad core, dual core, etc.) ? What
are other tricks that I can use to even more speed up the build?
Do you really use icecream/distcc on your daily test builds?
How about nicing/ionicing make on an idle system? Will it make any
difference?
Thanks a lot
Ozan Caglayan
next reply other threads:[~2009-09-15 8:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 8:22 Ozan Çağlayan [this message]
2009-09-16 2:35 ` Tricks to speed up kernel builds Thomas Fjellstrom
2009-09-16 2:49 ` david
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=4AAF4ECD.5010401@pardus.org.tr \
--to=ozan@pardus.org.tr \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.