From: "Markus F.X.J. Oberhumer" <markus@oberhumer.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
Johannes Stezenbach <js@sig21.net>,
richard -rw- weinberger <richard.weinberger@gmail.com>,
linux-btrfs@vger.kernel.org, linux-crypto@vger.kernel.org,
Artem Bityutskiy <dedekind1@gmail.com>,
Adrian Hunter <adrian.hunter@intel.com>,
David Woodhouse <dwmw2@infradead.org>,
Phillip Lougher <phillip@squashfs.org.uk>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH 0/3] Update LZO compression
Date: Tue, 09 Oct 2012 21:54:59 +0200 [thread overview]
Message-ID: <50748113.80408@oberhumer.com> (raw)
In-Reply-To: <20121009122614.569b9535.akpm@linux-foundation.org>
Hi Stephen,
On 2012-10-09 21:26, Andrew Morton wrote:
> On Sun, 7 Oct 2012 17:07:55 +0200
> "Markus F.X.J. Oberhumer" <markus@oberhumer.com> 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.
I'd ask you to include my "lzo-update" branch in linux-next:
git://github.com/markus-oberhumer/linux.git lzo-update
> 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.
The core compression and decompression code has been thoroughly tested, so I
do not expect major problems.
Good testing after the merge and feedback about build or performance issues
(and improvements!) is highly appreciated.
Many thanks,
Markus
--
Markus Oberhumer, <markus@oberhumer.com>, http://www.oberhumer.com/
next prev parent reply other threads:[~2012-10-09 19:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-07 15:07 [PATCH 0/3] Update LZO compression Markus F.X.J. Oberhumer
2012-10-07 15:08 ` [PATCH 1/3] lib/lzo: Rename lzo1x_decompress.c to lzo1x_decompress_safe.c Markus F.X.J. Oberhumer
2012-10-07 15:08 ` [PATCH 2/3] lib/lzo: Update LZO compression to current upstream version Markus F.X.J. Oberhumer
2012-10-07 15:09 ` [PATCH 3/3] lib/lzo: Optimize code for CPUs with inefficient unaligned access Markus F.X.J. Oberhumer
2012-10-09 19:26 ` [PATCH 0/3] Update LZO compression Andrew Morton
2012-10-09 19:54 ` Markus F.X.J. Oberhumer [this message]
2012-10-09 22:43 ` Stephen Rothwell
2012-10-11 11:41 ` Arnd Bergmann
2012-10-11 16:28 ` Markus F.X.J. Oberhumer
2012-12-21 2:03 ` Dan Magenheimer
-- strict thread matches above, loose matches on Subject: below --
2012-10-15 19:19 Seth Jennings
2012-10-15 23:45 ` Markus F.X.J. Oberhumer
2012-10-16 16:50 ` Seth Jennings
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=50748113.80408@oberhumer.com \
--to=markus@oberhumer.com \
--cc=adrian.hunter@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=dan.carpenter@oracle.com \
--cc=dan.magenheimer@oracle.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=js@sig21.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillip@squashfs.org.uk \
--cc=richard.weinberger@gmail.com \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.