From: "Roland" <devzero@web.de>
To: "Jan Engelhardt" <jengelh@medozas.de>
Cc: <linux-kernel@vger.kernel.org>, "Sam Ravnborg" <sam@ravnborg.org>
Subject: Re: [PATCH] Compress kernel modules on installation
Date: Sat, 27 Dec 2008 00:10:28 +0100 [thread overview]
Message-ID: <006201c967af$24c29740$6602a8c0@bui.materna.com> (raw)
In-Reply-To: alpine.LSU.2.00.0812262134270.12031@fbirervta.pbzchgretzou.qr
> On Friday 2008-12-26 21:23, Roland wrote:
>
>> what about some "make modules_install_compressed" instead ?
>>
>> as i have run out of diskspace quite often when installing test kernels,
>> i
>> think we really need a feature like this.
>>
>> i`d also favour the makefile approach.
>> why another kconfig option?
>>
>> jan`s patch looks clean and simple, but i think it`s a little bit
>> intrusive...
>
> Why so? module-ini
with "intrusive" i meant, that all modules are now compressed by default and
there is no switch to build them uncompressed.
so you change a long established default which may not be welcomed by
everyone and give no option for conservative people.
we should take care and not break things.
default uncompressed, compressed implented as an option is a better
strategy, imho.
discuss changing the default at a later time then.
roland
>>
>> regards
>> roland
>>
>> ps:
>> i`d use gzip without "-9" as this gives very little space savings. it
>> mostly
>> burns cpu and slows things down too much.
>> ( see
>> http://www.linuxjournal.com/files/linuxjournal.com/linuxjournal/articles/080/8051/8051f1.png
>
> Here is one that is tailored for kernel modules:
> http://tinyurl.com/8f2xta
> Looks pretty much like the one from LJ but of course, .ko files
> compress better than LJ :)
> Oh well.
next prev parent reply other threads:[~2008-12-26 23:10 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-26 20:23 [PATCH] Compress kernel modules on installation Roland
2008-12-26 21:09 ` Jan Engelhardt
2008-12-26 23:10 ` Roland [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2008-12-26 23:49 Roland
2008-02-25 21:42 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
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
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='006201c967af$24c29740$6602a8c0@bui.materna.com' \
--to=devzero@web.de \
--cc=jengelh@medozas.de \
--cc=linux-kernel@vger.kernel.org \
--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 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.