From: Kyle McMartin <kyle@infradead.org>
To: Theodore Tso <tytso@mit.edu>, Dave Jones <davej@redhat.com>,
Jan Beulich <jbeulich@novell.com>,
Sam Ravnborg <sam@ravnborg.org>,
linux-kernel@vger.kernel.org, ccache@lists.samba.org
Subject: Re: [REGRESSION] Recent change to kernel spikes out ccache/distcc
Date: Sun, 11 Jan 2009 16:48:37 -0500 [thread overview]
Message-ID: <20090111214837.GA21090@bombadil.infradead.org> (raw)
In-Reply-To: <20090108213157.GB922@mit.edu>
On Thu, Jan 08, 2009 at 04:31:58PM -0500, Theodore Tso wrote:
> On Thu, Jan 08, 2009 at 02:17:03PM -0500, Dave Jones wrote:
> >
> > Fedora rawhide users noticed this same problem this morning too,
> > when I pushed out a build that eats up a gig of diskspace thanks
> > to the number of modules we have, that are all afflicted by this problem.
> >
> > I'll have to revert ad7a953c for our builds to continue tracking mainline
> > without monopolising the diskspace in the Fedora build system.
>
> Note: you'll probably also have revert 9bb48247 (allow stripping of
> generated symbols under CONFIG_KALLSYMS_ALL) since I believe it
> depends on ad7a953c.
>
This doesn't appear to be the culprit. Or at least, doesn't fix the
problem.
make INSTALL_MOD_PATH=mods/ modules_install
with a distro kernel config (ie: Fedora's[1]) still results in
1.8GB of modules (willy checked that it wasn't a Fedora toolchain
bug by reproducing on a Debian system.)
As near as I can ascertain, this is limited to x86_64, at least on
Fedora:
kyle@localhost ~/misc $ for i in *.rpm; do echo $i; rpm
-qip $i | grep Size; done
kernel-2.6.29-0.25.rc0.git14.fc11.ppc64.rpm
Size : 124858478 License:
kernel-2.6.29-0.25.rc0.git14.fc11.ppc.rpm
Size : 66313693 License:
kernel-2.6.29-0.25.rc0.git14.fc11.x86_64.rpm
Size : 1041480317 License:
kernel-PAE-2.6.29-0.25.rc0.git14.fc11.i686.rpm
Size : 56252360 License:
x86_64 is an order of magnitude bigger than the rest, which have
identical debug options enabled.
regards, Kyle
next prev parent reply other threads:[~2009-01-11 21:49 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 15:15 Theodore Ts'o
2009-01-06 15:29 ` Jan Beulich
2009-01-06 17:33 ` Theodore Tso
2009-01-06 17:48 ` Sam Ravnborg
2009-01-06 18:04 ` Theodore Tso
2009-01-07 8:50 ` Jan Beulich
2009-01-07 11:31 ` Sam Ravnborg
2009-01-07 12:35 ` Jan Beulich
2009-01-07 13:23 ` Sam Ravnborg
2009-01-07 13:48 ` Jan Beulich
2009-01-07 20:06 ` Sam Ravnborg
2009-01-08 19:16 ` Kyle McMartin
2009-01-12 14:06 ` Gilles Espinasse
2009-01-06 17:53 ` Sam Ravnborg
2009-01-06 16:26 ` David Miller
2009-01-06 18:12 ` Theodore Tso
2009-01-06 22:09 ` Sam Ravnborg
2009-01-07 4:33 ` Theodore Tso
2009-01-07 5:10 ` Al Viro
2009-01-07 8:49 ` Jan Beulich
2009-01-07 14:03 ` Al Viro
2009-01-07 14:28 ` Jan Beulich
2009-01-07 14:37 ` Al Viro
2009-01-07 14:40 ` Jan Beulich
2009-01-07 13:12 ` Theodore Tso
2009-01-07 13:39 ` Jan Beulich
2009-01-07 14:28 ` Theodore Tso
2009-01-07 14:39 ` Jan Beulich
2009-01-08 19:17 ` Dave Jones
2009-01-08 21:31 ` Theodore Tso
2009-01-11 21:48 ` Kyle McMartin [this message]
2009-01-11 22:11 ` Theodore Tso
2009-01-11 22:51 ` Theodore Tso
2009-01-11 22:55 ` Kyle McMartin
2009-01-14 17:16 ` Peter Zijlstra
2009-01-15 9:11 ` Jan Beulich
2009-01-15 13:40 ` Theodore Tso
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=20090111214837.GA21090@bombadil.infradead.org \
--to=kyle@infradead.org \
--cc=ccache@lists.samba.org \
--cc=davej@redhat.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=tytso@mit.edu \
/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®