Re: [PATCH 0/3] Update LZO compression
From: Andrew Morton
Date: Tue Oct 09 2012 - 15:26:07 EST
On Sun, 7 Oct 2012 17:07:55 +0200
"Markus F.X.J. Oberhumer" <markus@xxxxxxxxxxxxx> wrote:
> As requested by akpm I am sending my "lzo-update" branch at
>
> git://github.com/markus-oberhumer/linux.git lzo-update
>
> to lkml as a patch series created by "git format-patch -M v3.5..lzo-update".
>
> You can also browse the branch at
>
> https://github.com/markus-oberhumer/linux/compare/lzo-update
>
> and review the three patches at
>
> https://github.com/markus-oberhumer/linux/commit/7c979cebc0f93dc692b734c12665a6824d219c20
> https://github.com/markus-oberhumer/linux/commit/10f6781c8591fe5fe4c8c733131915e5ae057826
> https://github.com/markus-oberhumer/linux/commit/5f702781f158cb59075cfa97e5c21f52275057f1
The changes look OK to me. Please ask Stephen to include the tree in
linux-next, for a 3.7 merge.
The changelog for patch 2/3 says:
: This commit updates the kernel LZO code to the current upsteam version
: which features a significant speed improvement - benchmarking the Calgary
: and Silesia test corpora typically shows a doubled performance in
: both compression and decompression on modern i386/x86_64/powerpc machines.
There are significant clients of the LZO library - crypto, btrfs,
jffs2, ubifs, squashfs and zcache. So let's give all those people a cc
and ask that they test the LZO changes once they land in linux-next.
For correctness and performance, please.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/