public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Robinson <andr345@gmail.com>
To: 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 08:52:44 +0100	[thread overview]
Message-ID: <1238053964.8304.24.camel@andreas-desktop> (raw)
In-Reply-To: <E1LmEqj-0001SN-6Y@be1.7eggert.dyndns.org>

On Tue, 2009-03-24 at 23:11 +0100, Bodo Eggert wrote:
> Andreas Robinson <andr345@gmail.com> wrote:
> 
> > I tried running the initramfs unpacking asynchronously (and earlier) but
> > ran into a curious problem: The parent thread stalled until
> > decompression was done. I don't know why - I made sure that the two
> > threads ran on different cores. Perhaps the parent was cache starved.
> 
> I could not stall my system by gzip</dev/urandom>/dev/null.
> Maybe you accidentally used vfork?

No, this was an in-kernel test. I used the Arjan's new async facility
which calls kthread_create().

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


  reply	other threads:[~2009-03-26  7:53 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 [this message]
2009-03-26 11:26     ` Bodo Eggert
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=1238053964.8304.24.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