public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard@openedhand.com>
To: Satyam Sharma <satyam.sharma@gmail.com>
Cc: Nitin Gupta <nitingupta910@gmail.com>,
	linux-kernel@vger.kernel.org, linux-mm-cc@laptop.org,
	Andrew Morton <akpm@linux-foundation.org>,
	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: Fri, 25 May 2007 14:38:24 +0100	[thread overview]
Message-ID: <1180100304.5864.60.camel@localhost.localdomain> (raw)
In-Reply-To: <a781481a0705250537o768c609evaf32d517444f7aca@mail.gmail.com>

On Fri, 2007-05-25 at 18:07 +0530, Satyam Sharma 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.
> 
> I hope you tested your _safe variant against this, Nitin has done away
> with the _unsafe version in this patch. 

I am.

> Also, are you using your crypto
> lzo-support + tcrypt changes ( http://lkml.org/lkml/2007/5/1/303 ) to
> benchmark these?

No, I'm putting the code into userspace and testing it there. Its not
difficult since there is little support needed from the kernel for
either set of code.

The tester runs each one in turn under the same circumstances from the
same binary and gives me a speed for each. Multiple runs return
consistent values and I'm being careful to make sure its an otherwise
idle machine and processes enough data to make sure there is no nasty
cache effects.

> > I am however still strongly of the opinion that we should just use the
> > version in -mm (which is my latest version).
> 
> Right, if the difference is anything >10%, code cleanup does lose
> its attractiveness.

Agreed, and I still have the security and maintainability concerns. Add
them all together and its more unattractive.

Cheers,

Richard


  reply	other threads:[~2007-05-25 13:38 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 [this message]
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
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=1180100304.5864.60.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