From: Sam Ravnborg <sam@ravnborg.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Steve Brokenshire <sbrokenshire@xestia.co.uk>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] Compress kernel modules on installation.
Date: Fri, 26 Dec 2008 20:48:33 +0100 [thread overview]
Message-ID: <20081226194833.GA8306@uranus.ravnborg.org> (raw)
In-Reply-To: <alpine.LSU.2.00.0812262026320.11203@fbirervta.pbzchgretzou.qr>
On Fri, Dec 26, 2008 at 08:30:19PM +0100, Jan Engelhardt wrote:
>
> On Tuesday 2008-02-26 12:28, Sam Ravnborg wrote:
> >>
> >> (I've sent this to the linux-kbuild and linux-kernel lists as this
> >> patch modifies the Makefile.modinst file. I also don't subscribe to the
> >> linux-kbuild and linux-kernel mailing lists so can I have any replies
> >> CC'ed to me please)
> >>
> >> This patch allows kernel modules to be compressed when 'make
> >> modules_install' is run after being copied to
> >> the /lib/module/<version>/<...> directory which is useful if you have
> >> module-init-tools installed with --enable-zlib. This patch adds an
> >> option (MODULE_COMPRESS) to the kernel configuration file (specifically
> >> init/Kconfig) so that the kernel modules will compressed if
> >> MODULE_COMPRESS is set.
>
> I recently started compressing my kernel modules and that saved me
> at least 70 MB of disk space on mostlyallmodconfig.
> (And no, the argument of disks being cheap is not so true with
> CF or SSD.)
> Distro is lazy and wants to wait for upstream to have it,
> so is there any chance of getting this proposal in?
Steve said he wanted to try to make the solution more
scalable so I am awaiting a new patch.
Sam
next prev parent reply other threads:[~2008-12-26 19:47 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 21:42 [PATCH] Compress kernel modules on installation Steve Brokenshire
2008-02-25 22:17 ` Oleg Verych
2008-02-25 22:19 ` Willy Tarreau
2008-02-25 22:32 ` Oleg Verych
2008-02-25 23:21 ` Willy Tarreau
2008-02-25 22:21 ` Willy Tarreau
2008-02-26 9:14 ` Adrian Bunk
2008-02-26 10:22 ` Willy Tarreau
2008-02-26 12:30 ` Adrian Bunk
2008-02-26 13:04 ` Willy Tarreau
2008-02-26 11:28 ` Sam Ravnborg
2008-04-01 19:42 ` Steve Brokenshire
2008-12-26 19:30 ` Jan Engelhardt
2008-12-26 19:48 ` Sam Ravnborg [this message]
2008-12-26 19:50 ` Jan Engelhardt
2008-12-26 22:57 ` Sam Ravnborg
2008-12-26 23:12 ` Jan Engelhardt
2009-01-18 21:04 ` Sam Ravnborg
2009-01-18 21:09 ` Arjan van de Ven
2009-01-18 21:15 ` Michael Tokarev
2009-01-18 21:18 ` Jan Engelhardt
2009-01-18 21:25 ` Michael Tokarev
2009-01-19 20:21 ` Jan Engelhardt
2009-01-20 3:30 ` Steve Brokenshire
2009-01-25 16:51 ` Steve Brokenshire
2009-01-25 18:02 ` Jan Engelhardt
2009-01-26 21:39 ` Steve Brokenshire
-- strict thread matches above, loose matches on Subject: below --
2008-12-26 20:23 Roland
2008-12-26 21:09 ` Jan Engelhardt
2008-12-26 23:10 ` Roland
2008-12-26 23:28 ` Bill Davidsen
2008-12-26 22:02 ` david
2008-12-26 21:15 ` Jan Engelhardt
2008-12-26 22:28 ` david
2008-12-26 23:23 ` Jan Engelhardt
2008-12-27 0:58 ` david
2009-01-01 8:27 ` Willy Tarreau
2008-12-26 23:49 Roland
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=20081226194833.GA8306@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=jengelh@medozas.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sbrokenshire@xestia.co.uk \
/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