From: Nuri Jawad <lkml@jawad.org>
To: Julian Seward <julian@valgrind.org>
Cc: Olivier Galibert <galibert@pobox.com>,
Ivan Novick <ivan@0x4849.net>,
Alistair John Strachan <s0348365@sms.ed.ac.uk>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: Linux Kernel Source Compression
Date: Tue, 23 May 2006 18:35:37 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0605231658001.28939@pc> (raw)
In-Reply-To: <200605231547.32420.julian@valgrind.org>
On Tue, 23 May 2006, Julian Seward wrote:
> It uses an adaptive huffman scheme devised by David Wheeler, which usually
> gets within 1% of the arithmetic coder that bzip1 used.
If that coder has patent issues, it shouldn't be used, of course,
regardless of performance.
> bzip2, especially the 1.0.X series, is superior to bzip1 in terms of speed,
> memory use, robustness against bad-case inputs, recoverability of data
> from damaged compressed streams, and that it can be used as a library.
Superior in most aspects, yes, but not regarding compression ratio.
Anyway, calling bzip2 a step backwards was a bit of provocation and not
really meant seriously, but it does have slightly reduced compression ratio.
Maybe bzip2 could be updated to make more use of today's fast CPUs? Much
larger dictionary or other computationally expensive improvements.
Regards, Nuri
next prev parent reply other threads:[~2006-05-23 16:35 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-21 14:35 Justin Piszcz
2006-05-21 18:40 ` Jan Engelhardt
2006-05-21 18:56 ` Kasper Sandberg
2006-05-21 19:28 ` Justin Piszcz
2006-05-22 2:05 ` Stefan Smietanowski
2006-05-21 19:03 ` Alistair John Strachan
2006-05-21 21:00 ` Chris Wedgwood
2006-05-21 21:22 ` Alistair John Strachan
2006-05-21 21:42 ` Sam Vilain
2006-05-21 21:57 ` Alistair John Strachan
2006-05-21 22:22 ` Sam Vilain
2006-05-21 22:29 ` Alistair John Strachan
2006-05-22 19:00 ` H. Peter Anvin
2006-05-21 21:59 ` Diego Calleja
2006-05-22 18:58 ` H. Peter Anvin
2006-05-22 19:07 ` Alistair John Strachan
2006-05-22 19:10 ` H. Peter Anvin
2006-05-22 19:15 ` Alistair John Strachan
2006-05-22 20:24 ` Jan Engelhardt
2006-05-22 20:41 ` H. Peter Anvin
2006-05-22 21:00 ` Alistair John Strachan
2006-05-22 21:04 ` H. Peter Anvin
2006-05-22 21:11 ` Joshua Hudson
2006-05-23 13:37 ` Jan Engelhardt
2006-05-23 2:16 ` Nuri Jawad
2006-05-23 2:55 ` Stefan Smietanowski
2006-05-23 14:15 ` Ivan Novick
2006-05-23 14:23 ` Olivier Galibert
2006-05-23 14:47 ` Julian Seward
2006-05-23 16:35 ` Nuri Jawad [this message]
2006-05-25 11:42 ` Jan Engelhardt
2006-05-31 22:51 ` Bill Davidsen
2006-05-23 13:38 ` Jan Engelhardt
2006-05-23 15:28 ` Alistair John Strachan
2006-05-31 22:56 ` Bill Davidsen
2006-05-26 4:11 ` Bruce Guenter
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=Pine.LNX.4.64.0605231658001.28939@pc \
--to=lkml@jawad.org \
--cc=galibert@pobox.com \
--cc=hpa@zytor.com \
--cc=ivan@0x4849.net \
--cc=jengelh@linux01.gwdg.de \
--cc=julian@valgrind.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s0348365@sms.ed.ac.uk \
/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
all inboxes | Powered by JetHome®