From: Dave Jones <davej@redhat.com>
To: Michal Marek <mmarek@suse.cz>
Cc: Lucas De Marchi <lucas.demarchi@profusion.mobi>,
Sam Ravnborg <sam@ravnborg.org>,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] kbuild: add target to install gzipped modules
Date: Fri, 30 Dec 2011 10:37:41 -0500 [thread overview]
Message-ID: <20111230153741.GA2167@redhat.com> (raw)
In-Reply-To: <4EFD913E.7010707@suse.cz>
On Fri, Dec 30, 2011 at 11:23:58AM +0100, Michal Marek wrote:
> On 29.12.2011 18:21, Dave Jones wrote:
> > On Thu, Dec 29, 2011 at 01:50:18PM -0200, Lucas De Marchi wrote:
> > > Add target in Makefile to compress the module after it's installed.
> > > Module-init-tools and libkmod can handle gzipped modules.
> > >
> > > This is not much useful for distributions because the package will gzip
> > > the modules and call depmod in a install rule.
> >
> > It might actually be a worthwhile thing for distributions.
> >
> > For a Fedora kernel, gzipping modules saves around 80MB of diskspace per
> > installed kernel. That the RPM is compressed is irrelevant, the on-disk
> > footprint is more interesting, given that the bulk of the modules installed
> > will never even be loaded.
>
> But it kills performance of the tools.
How often do you run depmod ?
If modprobe is a bottleneck, you have other problems.
Dave
next prev parent reply other threads:[~2011-12-30 15:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 15:50 [PATCH 1/2] kbuild: add target to install gzipped modules Lucas De Marchi
2011-12-29 15:50 ` [PATCH 2/2] kbuild: add target to install xz modules Lucas De Marchi
2011-12-29 16:42 ` [PATCH 1/2] kbuild: add target to install gzipped modules Michal Marek
2011-12-29 16:55 ` Lucas De Marchi
2011-12-29 17:05 ` Michal Marek
2011-12-29 17:35 ` Lucas De Marchi
2011-12-30 10:30 ` Michal Marek
2011-12-30 14:07 ` Lucas De Marchi
2011-12-29 17:21 ` Dave Jones
2011-12-30 10:23 ` Michal Marek
2011-12-30 15:37 ` Dave Jones [this message]
2011-12-30 16:40 ` Lucas De Marchi
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=20111230153741.GA2167@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=lucas.demarchi@profusion.mobi \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).