From: Edward Shishkin <edward@namesys.com>
To: Stefan Traby <stefan@hello-penguin.com>
Cc: Hans Reiser <reiser@namesys.com>,
Alexey Dobriyan <adobriyan@gmail.com>,
reiserfs-list@namesys.com, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@osdl.org>
Subject: Re: Reiser4 und LZO compression
Date: Mon, 28 Aug 2006 22:15:50 +0400 [thread overview]
Message-ID: <44F332D6.6040209@namesys.com> (raw)
In-Reply-To: <20060828173721.GA11332@hello-penguin.com>
Stefan Traby wrote:
> On Mon, Aug 28, 2006 at 10:06:46AM -0700, Hans Reiser wrote:
>
>
>>Hmm. LZO is the best compression algorithm for the task as measured by
>>the objectives of good compression effectiveness while still having very
>>low CPU usage (the best of those written and GPL'd, there is a slightly
>>better one which is proprietary and uses more CPU, LZRW if I remember
>>right. The gzip code base uses too much CPU, though I think Edward made
>
>
> I don't think that LZO beats LZF in both speed and compression ratio.
>
> LZF is also available under GPL (dual-licensed BSD) and was choosen in favor
> of LZO for the next generation suspend-to-disk code of the Linux kernel.
>
> see: http://www.goof.com/pcg/marc/liblzf.html
>
thanks for the info, we will compare them
next prev parent reply other threads:[~2006-08-28 18:15 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-27 0:34 Reiser4 und LZO compression Alexey Dobriyan
2006-08-27 8:04 ` Andrew Morton
2006-08-27 8:49 ` Ray Lee
2006-08-27 9:42 ` David Masover
2006-08-28 17:34 ` Jindrich Makovicka
2006-08-28 18:05 ` Edward Shishkin
2006-08-28 12:42 ` Jörn Engel
2006-08-29 13:14 ` PFC
2006-08-29 17:38 ` David Masover
2006-08-28 17:06 ` Hans Reiser
2006-08-28 17:37 ` Stefan Traby
2006-08-28 18:15 ` Edward Shishkin [this message]
2006-08-28 21:48 ` Nigel Cunningham
2006-08-28 23:32 ` Hans Reiser
2006-08-29 4:05 ` Jan Engelhardt
2006-08-29 5:41 ` Nigel Cunningham
2006-08-29 8:23 ` David Masover
2006-08-29 9:57 ` Nigel Cunningham
2006-08-29 11:09 ` Ray Lee
2006-08-29 11:38 ` Edward Shishkin
2006-08-29 22:03 ` Nigel Cunningham
2006-08-29 4:59 ` Paul Mundt
2006-08-29 5:47 ` Nigel Cunningham
2006-08-29 13:45 ` PFC
2006-08-29 14:38 ` Stefan Traby
2006-08-29 15:55 ` PFC
2006-08-29 17:56 ` Hans Reiser
2006-08-29 18:31 ` David Masover
2006-08-29 18:36 ` Gregory Maxwell
2006-08-29 19:11 ` David Masover
2006-08-29 19:38 ` Hans Reiser
2006-08-29 20:03 ` David Masover
2006-08-29 22:15 ` Toby Thain
2006-08-29 22:42 ` David Masover
2006-08-30 9:17 ` PFC
2006-08-30 10:45 ` David Masover
2006-08-30 16:50 ` Edward Shishkin
2006-08-30 16:55 ` Hans Reiser
2006-08-31 9:32 ` Clemens Eisserer
2006-08-31 12:00 ` Edward Shishkin
2006-08-31 15:14 ` Clemens Eisserer
2006-08-31 16:55 ` Hans Reiser
2006-08-31 18:08 ` Edward Shishkin
2006-08-31 19:22 ` David Masover
2006-08-29 15:41 ` Gregory Maxwell
2006-08-29 17:42 ` Hans Reiser
2006-08-29 9:29 ` Edward Shishkin
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=44F332D6.6040209@namesys.com \
--to=edward@namesys.com \
--cc=adobriyan@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=stefan@hello-penguin.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.