[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <34874167.ghObrToI03@fb07-iapwap2>
Date: Tue, 29 Jan 2013 12:43:20 +0100
From: Egon Alter <egon.alter@....net>
To: linux-arm-kernel@...ts.infradead.org
Cc: Russell King - ARM Linux <linux@....linux.org.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
Michal Marek <mmarek@...e.cz>, hyojun.im@....com,
raphael.andy.lee@...il.com, linux-kbuild@...r.kernel.org,
gunho.lee@....com, namhyung.kim@....com, x86@...nel.org,
linux-kernel@...r.kernel.org,
Josh Triplett <josh@...htriplett.org>,
Nitin Gupta <nitingupta910@...il.com>,
Richard Purdie <rpurdie@...nedhand.com>,
Ingo Molnar <mingo@...hat.com>,
Joe Millenbach <jmillenbach@...il.com>, chan.jeong@....com,
Kyungsik Lee <kyungsik.lee@....com>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Albin Tonnerre <albin.tonnerre@...e-electrons.com>,
CE Linux Developers List <celinux-dev@...ts.celinuxforum.org>,
minchan.kim@....com
Subject: Re: [RFC PATCH 0/4] Add support for LZ4-compressed kernels
Am Dienstag, 29. Januar 2013, 10:15:49 schrieb Russell King - ARM Linux:
> On Mon, Jan 28, 2013 at 02:25:10PM -0800, Andrew Morton wrote:
> > What's this "with enabled unaligned memory access" thing? You mean "if
> > the arch supports CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS"? If so,
> > that's only x86, which isn't really in the target market for this
> > patch, yes?
> >
> > It's a lot of code for a 50ms boot-time improvement. Does anyone have
> > any opinions on whether or not the benefits are worth the cost?
>
> Well... when I saw this my immediate reaction was "oh no, yet another
> decompressor for the kernel". We have five of these things already.
> Do we really need a sixth?
>
> My feeling is that we should have:
> - one decompressor which is the fastest
> - one decompressor for the highest compression ratio
> - one popular decompressor (eg conventional gzip)
the problem gets more complicated as the "fastest" decompressor usually
creates larger images which need more time to load from the storage, e.g. a
one MB larger image on a 10 MB/s storage (note: bootloaders often configure
the storage controllers in slow modes) gives 100 ms more boot time, thus
eating the gain of a "fast decompressor".
Egon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists