Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: wic creates ext4 images that read really slow in u-boot
Date: Tue, 19 Feb 2019 11:20:34 +0000	[thread overview]
Message-ID: <83ec17fa-88b0-04fa-adab-b402b10c6339@topic.nl> (raw)

Took me a while to figure out why my board took 90 seconds to boot suddenly.

The issue turned out to be the ext4 partition created by wic.

On a "wic" created ext4 disk, this is what u-boot does:

ZynqMP> load mmc 0:2 0x100000 /lib/firmware/fpga.bin
19311092 bytes read in 85529 ms (219.7 KiB/s)


Now if I boot the board rename and copy that file onto itself, then it's 
suddenly normal again when I reboot the board:

ZynqMP> load mmc 0:2 0x100000 /lib/firmware/fpga.bin
19311092 bytes read in 1426 ms (12.9 MiB/s)


I checked with other files, and it turns out that ANY big file written by wic 
will read very slow (at 200k/s) but if I make a copy from a running system, it 
suddenly reads fast.

I'm not knowledgeable on ext4, so any ideas what's being passed onto the image 
creation tool that causes this?


             reply	other threads:[~2019-02-19 16:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19 11:20 Mike Looijmans [this message]
2019-02-19 17:13 ` wic creates ext4 images that read really slow in u-boot Leon Woestenberg
2019-02-19 19:28   ` Andre McCurdy
2019-02-19 20:45     ` Leon Woestenberg
2019-02-20  9:12       ` Jack Mitchell
2019-02-20 10:42       ` Mike Looijmans
2019-02-20 15:44         ` Leon Woestenberg
2019-02-21 10:43         ` Burton, Ross
2019-02-20 10:55       ` Mike Looijmans
2019-02-21 14:33         ` Tom Rini

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=83ec17fa-88b0-04fa-adab-b402b10c6339@topic.nl \
    --to=mike.looijmans@topic.nl \
    --cc=openembedded-core@lists.openembedded.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