From: Johannes Stezenbach <js@sig21.net>
To: "Markus F.X.J. Oberhumer" <markus@oberhumer.com>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
chris.mason@fusionio.com, linux-btrfs@vger.kernel.org,
Nitin Gupta <ngupta@vflare.org>,
richard -rw- weinberger <richard.weinberger@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL v2] Update LZO compression
Date: Wed, 22 Aug 2012 12:34:43 +0200 [thread overview]
Message-ID: <20120822103443.GA15245@sig21.net> (raw)
In-Reply-To: <5033A78E.3080703@oberhumer.com>
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
On Tue, Aug 21, 2012 at 05:21:50PM +0200, Markus F.X.J. Oberhumer wrote:
> as suggested on the mailing list I have converted the updated LZO
> code into git, so please pull my "lzo-update" branch from
...
> [ Changes in v2: Optimize code for CPUs with inefficient unaligned
> access => significant speed increase on ARM ]
I can confirm that this new code runs at the same speed
as the current lzo code in the Linux kernel on
my ARM926EJ-S based platform. I only tested decompression,
using the attached hacky userspace code.
# time ./lzo-bench/old/unlzop <lzoimage >/dev/null
real 0m 0.29s
# time ./lzo-bench/new/unlzop <lzoimage >/dev/null
real 0m 0.29s
(where lzoimage is a Linux Image compressed with lzop)
So, from my side there are no more objections.
Thanks for doing this work, Markus.
Johannes
[-- Attachment #2: lzo-bench.tar.gz --]
[-- Type: application/octet-stream, Size: 35783 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: js@sig21.net (Johannes Stezenbach)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL v2] Update LZO compression
Date: Wed, 22 Aug 2012 12:34:43 +0200 [thread overview]
Message-ID: <20120822103443.GA15245@sig21.net> (raw)
In-Reply-To: <5033A78E.3080703@oberhumer.com>
On Tue, Aug 21, 2012 at 05:21:50PM +0200, Markus F.X.J. Oberhumer wrote:
> as suggested on the mailing list I have converted the updated LZO
> code into git, so please pull my "lzo-update" branch from
...
> [ Changes in v2: Optimize code for CPUs with inefficient unaligned
> access => significant speed increase on ARM ]
I can confirm that this new code runs at the same speed
as the current lzo code in the Linux kernel on
my ARM926EJ-S based platform. I only tested decompression,
using the attached hacky userspace code.
# time ./lzo-bench/old/unlzop <lzoimage >/dev/null
real 0m 0.29s
# time ./lzo-bench/new/unlzop <lzoimage >/dev/null
real 0m 0.29s
(where lzoimage is a Linux Image compressed with lzop)
So, from my side there are no more objections.
Thanks for doing this work, Markus.
Johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lzo-bench.tar.gz
Type: application/octet-stream
Size: 35783 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120822/ee82ee5e/attachment-0001.obj>
next prev parent reply other threads:[~2012-08-22 10:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 15:21 [GIT PULL v2] Update LZO compression Markus F.X.J. Oberhumer
2012-08-22 10:34 ` Johannes Stezenbach [this message]
2012-08-22 10:34 ` Johannes Stezenbach
2012-10-03 10:34 ` Markus F.X.J. Oberhumer
2012-10-03 10:48 ` richard -rw- weinberger
2012-10-03 21:01 ` Andrew Morton
2012-10-03 21:19 ` Andi Kleen
2012-10-03 21:32 ` Andrew Morton
2012-10-04 1:51 ` Andi Kleen
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=20120822103443.GA15245@sig21.net \
--to=js@sig21.net \
--cc=andi@firstfloor.org \
--cc=chris.mason@fusionio.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@oberhumer.com \
--cc=ngupta@vflare.org \
--cc=richard.weinberger@gmail.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 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.