From: "Markus F.X.J. Oberhumer" <markus@oberhumer.com>
To: linux-kernel@vger.kernel.org
Cc: Andi Kleen <andi@firstfloor.org>,
chris.mason@oracle.com, linux-btrfs@vger.kernel.org,
Nitin Gupta <ngupta@vflare.org>,
Richard Purdie <rpurdie@openedhand.com>
Subject: ANN: linux-kernel-lzo-2.06.20120123 - update LZO to v2.06
Date: Mon, 23 Jan 2012 17:19:40 +0100 [thread overview]
Message-ID: <4F1D889C.2050706@oberhumer.com> (raw)
In-Reply-To: <4F16DFB0.2060404@oberhumer.com>
Hi,
I've prepared a small package that updates the LZO version in the Linux
kernel to LZO v2.06.
Please get it from:
http://www.oberhumer.com/opensource/lzo/download/Testing/linux-kernel-lzo-2.06.20120123.tar.gz
As stated in the README, its main purpose is to allow easy benchmarking of the
latest LZO versions - these do feature some nice speed improvements, and while
I have done a lot of synthetic benchmarking I'm really very curious and
appreciate feedback on "real-world" performance numbers like usage in
btrfs and zram.
Share and enjoy,
Markus
http://www.oberhumer.com/opensource/lzo/
On 2012-01-18 16:05, Markus F.X.J. Oberhumer wrote:
> On 2012-01-13 01:28, Andi Kleen wrote:
>> Here's a slightly updated version of the BTRFS snappy interface.
>> snappy is a faster compression algorithm that provides similar
>> compression as LZO, but generally better performance.
>
> I'd like to note that the LZO version in the current Linux kernel is
> rather outdated - it seems to be based on the 2005 release.
>
> In fact the latest version LZO 2.06 does compress both slightly faster and
> better than snappy 1.0.4 when benchmarking the Calgary and Silesia
> compression corpus (tested with gcc 4.6 on Nehalem & Sandy Bridge).
>
> Furthermore please be aware that from a pure compression point of view
> snappy et al. are very close cousins of LZO (strictly byte-aligned LZ77)
> that mainly differ in implementation issues like using a table to
> number of branches - and indeed similar optimizations could be applied
> to any version.
>
> I'm not sure if there is an official kernel maintainer of LZO, but I'd
> offer to assist you updating to the latest version and eliminating
> any possible performance issues.
--
Markus Oberhumer, <markus@oberhumer.com>, http://www.oberhumer.com/
next prev parent reply other threads:[~2012-01-23 16:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 0:28 Updated btrfs/crypto snappy interface ready for merging Andi Kleen
2012-01-13 0:28 ` [PATCH 1/3] Add the snappy-c compressor to lib v2 Andi Kleen
2012-02-14 4:29 ` Mitch Harder
2012-02-14 19:52 ` Andi Kleen
2012-02-15 0:43 ` Mitch Harder
2012-01-13 0:28 ` [PATCH 2/3] BTRFS: Add snappy support v2 Andi Kleen
2012-01-13 0:28 ` [PATCH 3/3] Add snappy interface to crypto API Andi Kleen
2012-01-16 13:54 ` Updated btrfs/crypto snappy interface ready for merging Chris Mason
2012-01-17 8:44 ` Li Zefan
2012-01-17 8:46 ` Andi Kleen
2012-01-17 8:56 ` Li Zefan
2012-01-17 9:27 ` Li Zefan
2012-01-17 9:51 ` Andi Kleen
2012-01-17 9:07 ` David Sterba
2012-01-18 15:05 ` Markus F.X.J. Oberhumer
2012-01-23 16:19 ` Markus F.X.J. Oberhumer [this message]
2012-01-23 19:12 ` ANN: linux-kernel-lzo-2.06.20120123 - update LZO to v2.06 Nitin Gupta
2012-01-25 1:36 ` Andi Kleen
2012-10-09 8:39 ` David Sterba
2012-07-16 18:30 ` ANNOUNCE: linux-kernel-lzo-20120716 - update LZO Markus F.X.J. Oberhumer
2012-07-19 20:58 ` richard -rw- weinberger
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=4F1D889C.2050706@oberhumer.com \
--to=markus@oberhumer.com \
--cc=andi@firstfloor.org \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ngupta@vflare.org \
--cc=rpurdie@openedhand.com \
/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