Update LZO compression code for v3.9
Hi Linus,
please pull my "lzo-update" branch from
git://github.com/markus-oberhumer/linux.git lzo-update
You can also browse the branch at
https://github.com/markus-oberhumer/linux/compare/lzo-update
The LZO update actually had been approved by akpm for a 3.7 merge and is available in linux-next since October, but I've only recently learned that there is no automatic flow from linux-next to linux and I have to personally send a pull request.
Many thanks,
Markus
Summary:
========
Update the Linux kernel LZO compression and decompression code to the current upstream version which features significant performance improvements on modern machines.
$ git shortlog v3.8..lzo-update
Markus F.X.J. Oberhumer (3):
lib/lzo: Rename lzo1x_decompress.c to lzo1x_decompress_safe.c
lib/lzo: Update LZO compression to current upstream version
crypto: testmgr - update LZO compression test vectors$ git diff --stat v3.8..lzo-update crypto/testmgr.h | 38 +++-- include/linux/lzo.h | 15 +- lib/decompress_unlzo.c | 2 +- lib/lzo/Makefile | 2 +- lib/lzo/lzo1x_compress.c | 335 ++++++++++++++++++++++---------------- lib/lzo/lzo1x_decompress.c | 255 ----------------------------- lib/lzo/lzo1x_decompress_safe.c | 237 +++++++++++++++++++++++++++ lib/lzo/lzodefs.h | 38 +++-- 8 files changed, 488 insertions(+), 434 deletions(-)
Some *synthetic* benchmarks:
============================
x86_64 (Sandy Bridge), gcc-4.6 -O3, Silesia test corpus, 256 kB block-size:
compression speed decompression speed
LZO-2005 : 150 MB/sec 468 MB/sec LZO-2012 : 434 MB/sec 1210 MB/sec
i386 (Sandy Bridge), gcc-4.6 -O3, Silesia test corpus, 256 kB block-size:
compression speed decompression speed
LZO-2005 : 143 MB/sec 409 MB/sec LZO-2012 : 372 MB/sec 1121 MB/sec
armv7 (Cortex-A9), Linaro gcc-4.6 -O3, Silesia test corpus, 256 kB block-size:
compression speed decompression speed
LZO-2005 : 27 MB/sec 84 MB/sec LZO-2012 : 44 MB/sec 117 MB/sec **LZO-2013-UA : 47 MB/sec 167 MB/sec
Legend:
LZO-2005 : LZO version in current 3.8 kernel (which is based on
the LZO 2.02 release from 2005)
LZO-2012 : updated LZO version available in linux-next
**LZO-2013-UA : updated LZO version available in linux-next plus experimental
ARM Unaligned Access patch. This needs approval from some ARM maintainer ist NOT YET INCLUDED.
Signature · 1 line
Markus Oberhumer, <[email protected]>, http://www.oberhumer.com/
Quoted 4 lines · Markus F.X.J. Oberhumer
please pull my "lzo-update" branch from
git://github.com/markus-oberhumer/linux.gitlzo-update
I *really* want github (and other general hosting) pull requests to be for signed tags, so that I can see your gpg key and there is some real trail of who things got pulled from.
I prefer he signed tags even from trusted machines, because they allow for submitters to add comments directly for the merge, but for untrusted general hosting sites I will simply refuse to pull without them.
Linus
Quoted 7 lines · Linus Torvalds
Quoted 4 lines · Markus F.X.J. Oberhumer
please pull my "lzo-update" branch from
git://github.com/markus-oberhumer/linux.gitlzo-update
Quoted 8 lines
I *really* want github (and other general hosting) pull requests to be for signed tags, so that I can see your gpg key and there is some real trail of who things got pulled from.
I prefer he signed tags even from trusted machines, because they allow for submitters to add comments directly for the merge, but for untrusted general hosting sites I will simply refuse to pull without them.
Ok, I have pushed a signed tag "lzo-update-signature-20130226", but I'm not fully sure if that worked - at least
$ git verify-tag lzo-update-signature-20130226 gpg: Signature made Tue 26 Feb 2013 08:39:14 PM CET using DSA key ID 0B2043C9 gpg: Good signature from "Markus F.X.J. Oberhumer <[email protected]>"
and the tag does show up at
https://github.com/markus-oberhumer/linux/commits/lzo-update-signature-20130226
My public key 0B2043C9 is available on many PGP key servers, e.g.
http://pgp.mit.edu:11371/pks/lookup?search=markus+oberhumer
Cheers,
Markus
Quoted 3 lines
Linus
Signature · 1 line
Markus Oberhumer, <[email protected]>, http://www.oberhumer.com/