From: Bodo Eggert <7eggert@gmx.de>
To: Andreas Robinson <andr345@gmail.com>
Cc: 7eggert@gmx.de, Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: fastboot: unpacking initramfs faster
Date: Thu, 26 Mar 2009 12:26:35 +0100 (CET) [thread overview]
Message-ID: <alpine.LSU.0.999.0903261216550.5843@be1.lrz> (raw)
In-Reply-To: <1238053964.8304.24.camel@andreas-desktop>
On Thu, 26 Mar 2009, Andreas Robinson wrote:
> On Tue, 2009-03-24 at 23:11 +0100, Bodo Eggert wrote:
> > Andreas Robinson <andr345@gmail.com> wrote:
> > > I then looked at multithreaded decompression and found that neither gzip
> > > files nor deflate streams provide enough information (eg block lengths)
> > > to let you share the decompression among threads.
> > >
> > > It can be done of course, but obviously not without modifying file
> > > formats and userspace tools.
> > >
> > > (Thoughts of snowballs and hell presented themselves at this point.)
> >
> > Why not make a new set? http://7eggert.dyndns.org:8080/l/bgz.tar.gz
>
> Hmm, well if you think there is a chance of it being accepted, then
> sure! I'll cook something up, but will be looking to use LZO first since
> it's a bit faster to begin with.
It's small enough, and now I've updated it to support lzo and put a
license into the files.
Thinking about it: It's now very kernel-specific, other users might like a
block signature to make it robust against errors - e.g. in the middle of a
.tar.bgz file. I think I'll change that soon and put 0x55aa in front of
each block.
--
Borges sumus. Resistere inutile est.
next prev parent reply other threads:[~2009-03-26 11:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cj9yI-540-17@gated-at.bofh.it>
2009-03-24 22:11 ` Bodo Eggert
2009-03-26 7:52 ` Andreas Robinson
2009-03-26 11:26 ` Bodo Eggert [this message]
2009-03-26 11:57 ` Andreas Robinson
2009-03-26 12:56 ` Bodo Eggert
2009-03-26 16:05 ` Andreas Robinson
2009-03-24 7:39 Andreas Robinson
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=alpine.LSU.0.999.0903261216550.5843@be1.lrz \
--to=7eggert@gmx.de \
--cc=andr345@gmail.com \
--cc=arjan@infradead.org \
--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®