All of lore.kernel.org
 help / color / mirror / Atom feed
From: "roland" <devzero@web.de>
To: <nitingupta910@gmail.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] LZO de/compression support - take 4
Date: Sat, 26 May 2007 21:17:22 +0200	[thread overview]
Message-ID: <007801c79fca$7f1066e0$eeeea8c0@aldipc> (raw)

btw - does in-kernel lzo scale on SMP systems ?

is it a matter of lzo builtin compression or a matter of the component using 
in-kernel lzo compression ?

if i write/read data on reiser4 filesystem with lzo compression on - will 
all CPUs being used ?

just curious here, because i remember reading about a scale problem with zfs 
filesystem and gzip compression on solaris, so i'm just curious what to 
expect on linux.

regards
roland

ps:
btw - there is a smp aware lzop utility at lemley.net/lzop_patches/lzop.html




>Hi,
>
>This is kernel port of LZO1X compressor and LZO1X decompressor (safe
>version only).
>
>* Changes since 'take 3' (Full Changelog after this):
>1) Removed 'unsafe' decompressor - hence also do away with symlinks in
>Makefiles.
>2) Rolled back changes where I replaced COPY4 with memcpy() calls.
>This seemed to be causing too much perf. loss as shown by Richard's
>tests. Need perf. testing again to confirm that this patch has perf.
>comparable to original LZO code/Richard's patch.
>3) Some functions were inlined (DX2, DX3 etc.) - this also seemed to
>be one of factors for perf. loss. Changed them back Macros.
>4) Added back the 'register' keyword - again seemed to me one of
>factors for perf. loss.
>
>Once I pinpoint exact reason for bad perf., I will do above cleanups
>again. But this should not be reason for non-inclusion in mainline.
>These are only minor cleanups.
>
>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. 


             reply	other threads:[~2007-05-26 19:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-26 19:17 roland [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
2007-05-26 11:21       ` Nitin Gupta
2007-05-25 12:32 ` Satyam Sharma

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='007801c79fca$7f1066e0$eeeea8c0@aldipc' \
    --to=devzero@web.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nitingupta910@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.