public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Robinson <andr345@gmail.com>
To: Bodo Eggert <7eggert@gmx.de>
Cc: Arjan van de Ven <arjan@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: fastboot: unpacking initramfs faster
Date: Thu, 26 Mar 2009 12:57:11 +0100	[thread overview]
Message-ID: <1238068631.12756.23.camel@andreas-desktop> (raw)
In-Reply-To: <alpine.LSU.0.999.0903261216550.5843@be1.lrz>

On Thu, 2009-03-26 at 12:26 +0100, Bodo Eggert wrote:
> On Thu, 26 Mar 2009, Andreas Robinson wrote:
> > On Tue, 2009-03-24 at 23:11 +0100, Bodo Eggert wrote:
[snip]
> > > 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.

The file permissions are wrong, I'm not allowed to download it.

> 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.

I think we'll want an optional checksum of the compressed data.
Suppose bit 32 in the compressed block size field is set, the next field
is the block's Adler32 checksum.
(the adler32 source is in include/linux/zutil.h)


  reply	other threads:[~2009-03-26 11:57 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 ` fastboot: unpacking initramfs faster Bodo Eggert
2009-03-26  7:52   ` Andreas Robinson
2009-03-26 11:26     ` Bodo Eggert
2009-03-26 11:57       ` Andreas Robinson [this message]
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=1238068631.12756.23.camel@andreas-desktop \
    --to=andr345@gmail.com \
    --cc=7eggert@gmx.de \
    --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