mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: linux-kernel@vger.kernel.org, apiszcz@solarrain.com
Subject: Re: In response to kernel compression e-mail a few months ago.
Date: Sun, 14 Oct 2007 16:16:47 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0710141609380.3935@p34.internal.lan> (raw)
In-Reply-To: <Pine.LNX.4.64.0710142202030.22801@fbirervta.pbzchgretzou.qr>



On Sun, 14 Oct 2007, Jan Engelhardt wrote:

>
> On Oct 14 2007 15:53, Justin Piszcz wrote:
>>>
>>> What's with all these odd formats, and where is .zip? :)
>>> Somehow... have you tried lrzip?
>> $ apt-cache search lrzip
>> $
>>
>> I tried most of the main ones in the standard testing distribution within
>> Debian.
>
> Debian is not a solution to everything.
>
> http://ck.kolivas.org/apps/lrzip/
>

$ lrzip -L 9 linux-2.6.16.17.tar
Failed to open streams in rzip_fd
Fatal error - exiting

$ lrzip linux-2.6.16.17.tar -o linux-2.6.16.17.tar.lrz
Failed to open streams in rzip_fd
Fatal error - exiting

$ lrzip -l -L 9 linux-2.6.16.17.tar
Bus error

   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
22176 abc       20   0 2197m 156m  75m R   93  4.8   0:09.17 lrzip

It must grow to 3.0GB and die (this is on an x86 host)..

$ lrzip -w 1 -l -L 9 linux-2.6.16.17.tar
linux-2.6.16.17.tar - compression ratio 3.127

$ du -sh *lrz
72M     linux-2.6.16.17.tar.lrz

$ lrzip -w 10 -l -L 9 linux-2.6.16.17.tar
linux-2.6.16.17.tar - compression ratio 3.380
$ du -sh *lrz
67M     linux-2.6.16.17.tar.lrz

Does not seem to come close unless I am doing something wrong.

Also, 7z can compress/decompress on stdin and it is multi-threaded (uses 
1.8-2.2 CPU/cores).

>> note that lrzip cannot operate on stdin/stdout

Justin.

  reply	other threads:[~2007-10-14 20:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-14 19:34 Justin Piszcz
2007-10-14 19:46 ` Jan Engelhardt
2007-10-14 19:53   ` Justin Piszcz
2007-10-14 20:04     ` Jan Engelhardt
2007-10-14 20:16       ` Justin Piszcz [this message]
2007-10-14 20:50   ` Al Viro
2007-10-14 20:58     ` Justin Piszcz
2007-10-14 21:48       ` Jan Engelhardt
2007-10-14 22:28         ` Justin Piszcz
2007-10-16 13:19       ` Denys Vlasenko
2007-10-16 13:31         ` Andreas Schwab
2007-10-16 20:54           ` Denys Vlasenko
2007-10-16 14:22         ` Jan Engelhardt

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.0710141609380.3935@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=apiszcz@solarrain.com \
    --cc=jengelh@computergmbh.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

all inboxes | Powered by JetHome®