From: Peter Korsgaard <jacmet@sunsite.dk>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] add lzop decompression support
Date: Thu, 19 Nov 2009 13:38:00 +0100 [thread overview]
Message-ID: <87iqd6itav.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <OF9CF77FC9.85C6CB90-ONC1257673.0042BA5F-C1257673.00442108@transmode.se> (Joakim Tjernlund's message of "Thu\, 19 Nov 2009 13\:24\:09 +0100")
>>>>> "Joakim" == Joakim Tjernlund <joakim.tjernlund@transmode.se> writes:
Hi,
>> Lzop doesn't compress as good as gzip (~10% worse), but
>> decompression is very fast (~0.7s faster here on a slow ppc). The
>> lzop decompression code is based on Albin Tonnerre's recent ARM
>> Linux lzo support patch.
Joakim> Perhaps you want to have a look at the patch I just sent:
Joakim> [PATCH RFC] zlib: Optimize decompression
Yes, I noticed (and your corresponding kernel patch). I'll give it a
try, but it's probably still slower than lzo.
Thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-11-19 12:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 10:37 [U-Boot] [PATCH] add lzop decompression support Peter Korsgaard
2009-11-19 12:24 ` Joakim Tjernlund
2009-11-19 12:38 ` Peter Korsgaard [this message]
2009-11-27 9:06 ` Peter Korsgaard
2009-12-05 0:30 ` Wolfgang Denk
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=87iqd6itav.fsf@macbook.be.48ers.dk \
--to=jacmet@sunsite.dk \
--cc=u-boot@lists.denx.de \
/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