From: Stephen Cameron <steve.cameron@hp.com>
To: linux-kernel@vger.kernel.org
Subject: How to speed up building of modules?
Date: Fri, 4 Apr 2003 14:57:40 +0600 [thread overview]
Message-ID: <20030404085740.GA10052@zuul.cca.cpqcorp.net> (raw)
Hi
I'm wondering if you guys know any tricks to speed up building
of linux kernel modules.
First, some background.
We have to put out binary HBA driver modules for a variety
of linux distributions for things like driver diskettes, to allow
new drivers to be used during initial install. (I'm thinking
of the cciss, cpqarray and cpqfc drivers.)
With all the distributions, and differnent
offerings of distributions, and errata kernels... today, I count
almost 40 distinct kernels we're trying to support, not counting the
mainline development on kernel.org, and not counting multiple
config file variations for each of those 40 or so kernels.
The main catch seems to be the symbol checksums. In order for those
to match (and I'm not too interested in subverting those), the
config files used during the compile need to be very similar. That
means building lots and lots of modules. (Think about all the
modules which are enabled in redhat's typical default config files.)
This takes time. Mulitply 3 drivers * ~40 kernels * several config
files, and pretty soon... well, pretty soon you don't remember
what "preety soon" means.
It would be VERY nice if I could find a way to build only the modules
I care about and not all the rest, which add hours and hours.
It seems that some things in the config file can be turned off without
harm, but it's not clear how I can know whether it's safe to turn a module
off Also, sometimes I need to make changes to the Config.in files,
add options, etc. Ccache hasn't helped. (I think because the different
config files use different compiler flags, and otherwise the kernels
just aren't the same.)
Any ideas?
Thanks,
-- steve
next reply other threads:[~2003-04-04 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 8:57 Stephen Cameron [this message]
2003-04-04 21:17 ` Richard B. Johnson
2003-04-04 22:05 ` Robert White
2003-04-05 7:48 ` Sam Ravnborg
2003-04-06 22:09 ` Bernd Petrovitsch
2003-04-07 14:27 Cameron, Steve
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=20030404085740.GA10052@zuul.cca.cpqcorp.net \
--to=steve.cameron@hp.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®