From: Roman Mamedov <rm@romanrm.ru> To: Johannes Stezenbach <js@sig21.net> Cc: "Markus F.X.J. Oberhumer" <markus@oberhumer.com>, 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 Purdie <rpurdie@openedhand.com>, richard -rw- weinberger <richard.weinberger@gmail.com>, linux-arm-kernel@lists.infradead.org Subject: Re: [GIT PULL] Update LZO compression Date: Thu, 16 Aug 2012 23:25:49 +0600 [thread overview] Message-ID: <20120816232549.4d14a6aa@natsu> (raw) In-Reply-To: <20120816150647.GA22010@sig21.net> [-- Attachment #1: Type: text/plain, Size: 1513 bytes --] On Thu, 16 Aug 2012 17:06:47 +0200 Johannes Stezenbach <js@sig21.net> wrote: > Well, ~2x speedup on x86 is certainly a good achievement, but there > are more ARM based devices than there are PCs, and I guess many > embedded devices use lzo compressed kernels and file systems > while I'm not convinced many PCs rely on lzo in the kernel. Keep in mind that a major user of LZO is the BTRFS filesystem, and I believe it is used much more often on larger machines than on ARM, in fact it had problems operating on ARM at all, until quite recently. > I know everyone's either busy or on vacation, but it would > be so cool if someone could test on a more modern ARM core, > with the userspace test code I posted it should be easy to do. I have locked the Allwinner A10 CPU in my Mele A2000 to 60 MHz using cpufreq-set, and ran your test. rnd.lzo is a 9 MB file from /dev/urandom compressed with lzo. There doesn't seem to be a significant difference between all three variants. # time for i in {1..20}; do old/unlzop < rnd.lzo >/dev/null ; done real 0m11.353s user 0m3.060s sys 0m8.170s # time for i in {1..20}; do new/unlzop < rnd.lzo >/dev/null ; done real 0m11.416s user 0m3.030s sys 0m8.200s # time for i in {1..20}; do test/unlzop < rnd.lzo >/dev/null ; done real 0m11.310s user 0m3.100s sys 0m8.150s -- With respect, Roman ~~~~~~~~~~~~~~~~~~~~~~~~~~~ "Stallman had a printer, with code he could not see. So he began to tinker, and set the software free." [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 198 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: rm@romanrm.ru (Roman Mamedov) To: linux-arm-kernel@lists.infradead.org Subject: [GIT PULL] Update LZO compression Date: Thu, 16 Aug 2012 23:25:49 +0600 [thread overview] Message-ID: <20120816232549.4d14a6aa@natsu> (raw) In-Reply-To: <20120816150647.GA22010@sig21.net> On Thu, 16 Aug 2012 17:06:47 +0200 Johannes Stezenbach <js@sig21.net> wrote: > Well, ~2x speedup on x86 is certainly a good achievement, but there > are more ARM based devices than there are PCs, and I guess many > embedded devices use lzo compressed kernels and file systems > while I'm not convinced many PCs rely on lzo in the kernel. Keep in mind that a major user of LZO is the BTRFS filesystem, and I believe it is used much more often on larger machines than on ARM, in fact it had problems operating on ARM at all, until quite recently. > I know everyone's either busy or on vacation, but it would > be so cool if someone could test on a more modern ARM core, > with the userspace test code I posted it should be easy to do. I have locked the Allwinner A10 CPU in my Mele A2000 to 60 MHz using cpufreq-set, and ran your test. rnd.lzo is a 9 MB file from /dev/urandom compressed with lzo. There doesn't seem to be a significant difference between all three variants. # time for i in {1..20}; do old/unlzop < rnd.lzo >/dev/null ; done real 0m11.353s user 0m3.060s sys 0m8.170s # time for i in {1..20}; do new/unlzop < rnd.lzo >/dev/null ; done real 0m11.416s user 0m3.030s sys 0m8.200s # time for i in {1..20}; do test/unlzop < rnd.lzo >/dev/null ; done real 0m11.310s user 0m3.100s sys 0m8.150s -- With respect, Roman ~~~~~~~~~~~~~~~~~~~~~~~~~~~ "Stallman had a printer, with code he could not see. So he began to tinker, and set the software free." -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120816/d1a5e749/attachment.sig>
next prev parent reply other threads:[~2012-08-16 17:25 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-13 23:44 [GIT PULL] Update LZO compression Markus F.X.J. Oberhumer 2012-08-14 3:15 ` Andi Kleen 2012-08-14 10:10 ` Markus F.X.J. Oberhumer 2012-08-14 12:39 ` Johannes Stezenbach 2012-08-14 12:39 ` Johannes Stezenbach 2012-08-15 12:02 ` Markus F.X.J. Oberhumer 2012-08-15 12:02 ` Markus F.X.J. Oberhumer 2012-08-15 14:45 ` Johannes Stezenbach 2012-08-15 14:45 ` Johannes Stezenbach 2012-08-16 6:27 ` Markus F.X.J. Oberhumer 2012-08-16 6:27 ` Markus F.X.J. Oberhumer 2012-08-16 15:06 ` Johannes Stezenbach 2012-08-16 15:06 ` Johannes Stezenbach 2012-08-16 17:25 ` Roman Mamedov [this message] 2012-08-16 17:25 ` Roman Mamedov 2012-08-16 17:52 ` Andi Kleen 2012-08-16 17:52 ` Andi Kleen 2012-08-16 18:18 ` Geert Uytterhoeven 2012-08-16 18:18 ` Geert Uytterhoeven 2012-08-16 18:55 ` james northrup 2012-08-16 22:17 ` Andi Kleen 2012-08-16 22:17 ` Andi Kleen 2012-08-17 1:23 ` Mitch Harder 2012-08-17 1:23 ` Mitch Harder 2012-09-07 21:31 ` Andi Kleen 2012-09-07 21:31 ` Andi Kleen 2012-08-16 18:57 ` james northrup 2012-08-16 15:21 ` Jeff Garzik 2012-08-16 15:21 ` Jeff Garzik 2012-08-16 16:20 ` Andi Kleen 2012-08-16 16:20 ` Andi Kleen 2012-08-16 16:48 ` Jeff Garzik 2012-08-16 16:48 ` Jeff Garzik 2012-08-16 17:22 ` Johannes Stezenbach 2012-08-16 17:22 ` Johannes Stezenbach
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=20120816232549.4d14a6aa@natsu \ --to=rm@romanrm.ru \ --cc=andi@firstfloor.org \ --cc=chris.mason@fusionio.com \ --cc=js@sig21.net \ --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 \ --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: linkBe 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.