public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard@openedhand.com>
To: Nitin Gupta <nitingupta910@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-mm-cc@laptop.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Satyam Sharma <satyam.sharma@gmail.com>,
	Andrey Panin <pazke@donpac.ru>, Bret Towe <magnade@gmail.com>,
	Michael-Luke Jones <mlj28@cam.ac.uk>
Subject: Re: [RFC] LZO de/compression support - take 4
Date: Sat, 26 May 2007 11:28:45 +0100	[thread overview]
Message-ID: <1180175325.5856.23.camel@localhost.localdomain> (raw)
In-Reply-To: <4cefeab80705250557w1baee0afn255e37436b6545a@mail.gmail.com>

Hi Nitin,

On Fri, 2007-05-25 at 18:27 +0530, Nitin Gupta wrote:
> On 5/25/07, Richard Purdie <richard@openedhand.com> wrote:
> > On Fri, 2007-05-25 at 17:15 +0530, Nitin Gupta wrote:
> > > Richard, can you please provide perf. results for this patch also?
> > > Also, can you please mail back latest version of your LZO patch? In
> > > meantime, I will try to include benchmarking support to the
> > > 'compress-test' module.
> >
> > This version is 15% slower at decompression and about equal on
> > compression.
> >
> 
> If you don't mind, can you please try patch attached now? I have now
> also rolled back that cpu_to_le16() change as Satyam suggested. I see
> no other reason for this perf. loss as I made no other change!
> 
> Also, can you please verify if you are comparing your _safe_ version
> with this patch? This patch does not include unsafe version and the
> safe one is simply called lzo1x_decompress().

I've been looking at my benchmark figures and I think I've found why the
figures for my version were different to yours. Its not your code which
is at fault, its the way it was hooked into the benchmarking program.
The compiler was inlining some parts which it shouldn't have been
allowed to do, sorry :-/.

With that issue corrected, decompression is the same speed however
compression is showing about a 9% performance loss compared to my kernel
patch.

I did some diffs of the assembler outputted by our two versions (mine
matches minilzo). For decompression the output is effectively identical.
For compression, there are significant differences. If I add a noinline
attribute to lzo1x_compress_worker, that removes a lot of them (and
boosts speed a bit) but there are still differences. Ideally, I'd like
to understand why.

Regards,

Richard



  parent reply	other threads:[~2007-05-26 10:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-25 11:45 [RFC] LZO de/compression support - take 4 Nitin Gupta
2007-05-25 12:00 ` Michael-Luke Jones
2007-05-25 12:10 ` Richard Purdie
2007-05-25 12:37   ` Satyam Sharma
2007-05-25 13:38     ` Richard Purdie
2007-05-25 16:55       ` Daniel Hazelton
2007-05-25 18:45         ` Daniel Hazelton
2007-05-25 19:35           ` Satyam Sharma
2007-05-28  8:18             ` Daniel Hazelton
2007-05-28  8:37               ` Nitin Gupta
2007-05-28  8:43                 ` Daniel Hazelton
2007-05-28  9:08                   ` Nitin Gupta
2007-05-28  9:21                     ` Daniel Hazelton
2007-05-28  9:46                       ` Nitin Gupta
2007-05-28  9:58                         ` Daniel Hazelton
2007-05-25 12:57   ` Nitin Gupta
2007-05-25 13:33     ` Richard Purdie
2007-05-26 10:28     ` Richard Purdie [this message]
2007-05-26 11:21       ` Nitin Gupta
2007-05-25 12:32 ` Satyam Sharma
  -- strict thread matches above, loose matches on Subject: below --
2007-05-26 19:17 roland

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=1180175325.5856.23.camel@localhost.localdomain \
    --to=richard@openedhand.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm-cc@laptop.org \
    --cc=magnade@gmail.com \
    --cc=mlj28@cam.ac.uk \
    --cc=nitingupta910@gmail.com \
    --cc=pazke@donpac.ru \
    --cc=satyam.sharma@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox