All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] improve boot time with standalone images
Date: Mon, 23 Dec 2013 05:06:24 +0100	[thread overview]
Message-ID: <52B7B6C0.6060602@gmail.com> (raw)
In-Reply-To: <52B74B0F.702@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 897 bytes --]

On 22.12.2013 21:26, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> Hello, all. While testing on raspberry pi using standalone image I've
> noticed that all file operations were sluggish. The culprit was tar that
> we use as a filesystem for memdisk which requires complete scan to find
> one file. On most systems it's a minor time penalty but on raspberry pi
> it almost halved boot time. I propose a specialised compact and fast
> uncompressed read-only filesystem by storing filenames in sorted array
> and using binary search. It's a pretty big change but I feel like it's
> worth to be put into 2.02.
> Does anybody disagree?
> 
After discussing with Leif Lindholm, it was found out that real culprit
was disabled cache on U-boot port.
Time to console
Cached, tar: 0.5s
Cached, greffs: 0.3s
Uncached tar: 7.3s
Uncached greffs: 4.3s
On coreboot the speed-up is only 4ms


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]

      reply	other threads:[~2013-12-23  4:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-22 20:26 [PATCH] improve boot time with standalone images Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-23  4:06 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]

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=52B7B6C0.6060602@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.