From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Rob Landley <rob@landley.net>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
Matt Mackall <mpm@selenic.com>,
Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
Subject: Re: [PATCH] skip initramfs check
Date: Mon, 21 Nov 2005 04:23:50 -0200 [thread overview]
Message-ID: <20051121062350.GA24381@logos.cnet> (raw)
In-Reply-To: <200511210130.55774.rob@landley.net>
Hi Rob,
On Mon, Nov 21, 2005 at 01:30:55AM -0600, Rob Landley wrote:
> On Thursday 17 November 2005 08:14, Marcelo Tosatti wrote:
> > Hi,
> >
> > The initramfs check at populate_rootfs() can consume significant time
> > (several seconds) on slow/embedded platforms, since it has to decompress
> > the image.
>
> Query: is the problem that a big initramfs image is being unpacked more than
> once, or is unpacking an empty initramfs image (134 bytes) causing a
> significant delay?
The problem is a big non-initramfs RAMDISK image (used for root mountpoint on this
particular embedded platform), that is decompressed more than once:
- during the initramfs check, which fails because it is not initramfs.
- during the real RAMDISK decompression to memory.
> I'm fairly certain that back in 1990 I could unzip 134 bytes on my 33 mhz 386
> running dos in a fraction of a second. What's the use case here?
So the issue is not the empty initramfs image (which BTW could probably
be made unecessary?), but a 10Mb RAMDISK image being decompressed by a
48Mhz PPC, which takes quite a few seconds.
Need to rework the patch to use a __setup option as Andrew suggested.
next prev parent reply other threads:[~2005-11-21 11:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 14:14 [PATCH] skip initramfs check Marcelo Tosatti
2005-11-17 22:56 ` Andrew Morton
2005-11-21 7:30 ` Rob Landley
2005-11-21 6:23 ` Marcelo Tosatti [this message]
2005-11-21 15:04 ` Rob Landley
2005-11-21 15:50 ` Matt Mackall
2005-11-21 10:49 ` Marcelo Tosatti
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=20051121062350.GA24381@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=rob@landley.net \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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