On Tue, Feb 26, 2013 at 10:58:02PM +0100, Peter Korsgaard wrote: > >>>>> "Nicolas" == Nicolas Pitre <nico@xxxxxxxxxxx> writes: > > Hi, > > >> Did you actually *try* the new LZO version and the patch (which is attached > >> once again) as explained in https://lkml.org/lkml/2013/2/3/367 ? > >> > >> Because the new LZO version is faster than LZ4 in my testing, at least > >> when comparing apples with apples and enabling unaligned access in > >> BOTH versions: > >> > >> armv7 (Cortex-A9), Linaro gcc-4.6 -O3, Silesia test corpus, 256 kB block-size: > >> > >> compression speed decompression speed > >> > >> LZO-2012 : 44 MB/sec 117 MB/sec no unaligned access > >> LZO-2013-UA : 47 MB/sec 167 MB/sec Unaligned Access > >> LZ4 r88 UA : 46 MB/sec 154 MB/sec Unaligned Access > > Nicolas> To be fair, you should also take into account the compressed > Nicolas> size of a typical ARM kernel. Sometimes a slightly slower > Nicolas> decompressor may be faster overall if the compressed image to > Nicolas> work on is smaller. > > Yes, but notice that lzo compressed BETTER than lz4 - E.G. from the > introduction mail: > > 1. ARMv7, 1.5GHz based board > Kernel: linux 3.4 > Uncompressed Kernel Size: 14MB > Compressed Size Decompression Speed > LZO 6.7MB 21.1MB/s > LZ4 7.3MB 29.1MB/s, 45.6MB/s(UA) Well, until someone can put all the pieces together so that a reasonably meaningful test between: - The new LZO code - The new LZ4 code then you're all comparing different things. TBH, I'm disappointed that all the comments about this from the previous posting of LZ4 have been totally ignored, and we _still_ don't really have this information. It seems like replying to these threads is a waste of time. So... for a selected kernel version of a particular size, can we please have a comparison between the new LZO code and this LZ4 code, so that we can see whether it's worth updating the LZO code or replacing the LZO code with LZ4? -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
