mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Where's the bzip2 compressed linux-kernel patch?
Date: Sat, 18 Oct 2003 15:38:35 -0500	[thread overview]
Message-ID: <200310181538.35301.rob@landley.net> (raw)
In-Reply-To: <20031018164337.GB11066@wohnheim.fh-wedel.de>

On Saturday 18 October 2003 11:43, Jörn Engel wrote:
> On Sat, 18 October 2003 00:18:21 -0500, Rob Landley wrote:
> > I just rewrote bunzip2 for busybox in about 500 lines of C (and a good
> > chunk of that's comments), which comiles to a bit under 7k.
>
> 5140 on my machine, compared to 9436 for the stock decompress.o.  Nice.
>
> Does it survive the bzip2 testcases?

The decompression-side ones, yes.  (Modulo different command line arguments, 
and that I didn't implement the "small mode" that's slower but uses less 
memory.  That would probably only add a couple hundred bytes, and I could 
make it a compile time option, but I just haven't gotten around to it yet.  
If somebody wants to send me a patch... :)

Mostly I've been repeatedly extracting linux-2.6.0-test6.tar.bz2 as my 
testcase.  Much more of a workout. :)

> > P.S.  If you're curious about the micro-bunzip code, it's in busybox CVS:
> > http://www.busybox.net/cgi-bin/cvsweb/busybox/archival/libunarchive/decom
> >press_bunzip2.c
>
> Not pretty with 80 columns, but it looks good at first glance.

Manuel Novoa submitted a patch that sped things up over 10% (seriously cool, 
that's why we're faster than the original), but broke the 80 column thing 
(mostly a couple return statements that need to be on the next line).

I'm happy to take a patch to clean it up. :)

> And surely more fun to work on than the zlib-inspired code from Julian.

That was the original reason for doing this, yes. :)

Eric Anderson pointed me to the new home of the kernel bunzip patch, which is 
at "http://shepard.kicks-ass.net/~cc/", and I'll take a stab at porting it to 
2.6.0-test8 as the mood strikes me. :)

> Jörn

Rob

  reply	other threads:[~2003-10-18 20:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-18  5:18 Rob Landley
2003-10-18  5:30 ` Nick Piggin
2003-10-18 11:39   ` Daniel Egger
2003-10-19  0:51     ` Nick Piggin
2003-10-19 10:45       ` Michael Buesch
2003-10-19 21:04         ` Willy Tarreau
2003-10-19 21:27           ` Michael Buesch
2003-10-20  0:00           ` Rob Landley
2003-10-20  4:28             ` Willy Tarreau
2003-10-20  4:52               ` Valdis.Kletnieks
2003-10-20  5:47               ` Rob Landley
2003-10-20 11:55                 ` Willy Tarreau
2003-10-19 22:15         ` Rob Landley
2003-10-18  6:05 ` Erik Andersen
2003-10-18 16:43 ` Jörn Engel
2003-10-18 20:38   ` Rob Landley [this message]
2003-10-20  8:31     ` Jörn Engel
2003-10-20  9:41       ` Rob Landley

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=200310181538.35301.rob@landley.net \
    --to=rob@landley.net \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-kernel@vger.kernel.org \
    /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

Powered by JetHome