linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 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 17:06:47 +0200	[thread overview]
Message-ID: <20120816150647.GA22010@sig21.net> (raw)
In-Reply-To: <502C92C3.7090701@oberhumer.com>

On Thu, Aug 16, 2012 at 08:27:15AM +0200, Markus F.X.J. Oberhumer wrote:
> On 2012-08-15 16:45, Johannes Stezenbach wrote:
> > 
> > I made the attached quick hack userspace code
> > using ARM kernel headers and barebox unlzop code.
> > (new == your new code, old == linux-3.5 git, test == new + your suggested change)
> > (sorry I had no time to clean it up)
> 
> My suggested COPY4 replacement probably has a lot of load stalls - maybe some
> ARM expert could have a look and suggest a more efficient implementation.
> 
> In any case, I still would like to see the new code in linux-next because
> of the huge improvements on other modern CPUs.

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.

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.


Johannes

  reply	other threads:[~2012-08-16 15:07 UTC|newest]

Thread overview: 18+ 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-15 12:02   ` Markus F.X.J. Oberhumer
2012-08-15 14:45     ` Johannes Stezenbach
2012-08-16  6:27       ` Markus F.X.J. Oberhumer
2012-08-16 15:06         ` Johannes Stezenbach [this message]
2012-08-16 17:25           ` Roman Mamedov
2012-08-16 17:52             ` Andi Kleen
2012-08-16 18:18               ` Geert Uytterhoeven
     [not found]                 ` <CAPkEcwgv6f5B+Mrw7kzrHcZ5JZ+Yr0o=bLdoFqCB-e4CLiVx5A@mail.gmail.com>
2012-08-16 22:17                   ` Andi Kleen
2012-08-17  1:23                     ` Mitch Harder
2012-09-07 21:31                   ` Andi Kleen
2012-08-16 15:21         ` Jeff Garzik
2012-08-16 16:20           ` Andi Kleen
2012-08-16 16:48             ` Jeff Garzik
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=20120816150647.GA22010@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 \
    --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;
as well as URLs for NNTP newsgroup(s).