From: Leon Woestenberg <leon@sidebranch.com>
To: Mike Looijmans <mike.looijmans@topic.nl>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: wic creates ext4 images that read really slow in u-boot
Date: Tue, 19 Feb 2019 18:13:15 +0100 [thread overview]
Message-ID: <CAMjhiJjO0+0=_6HOmVM67U0nnbW=iu-FiMTzJBe4ZCvceuguuA@mail.gmail.com> (raw)
In-Reply-To: <83ec17fa-88b0-04fa-adab-b402b10c6339@topic.nl>
[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]
Hello Mike,
sounds familiar.
On Tue, 19 Feb 2019 at 17:55, Mike Looijmans <mike.looijmans@topic.nl>
wrote:
> 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.
I suspect it's not WIC's fault.
> 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 0x10000
> I'm not knowledgeable on ext4, so any ideas what's being passed onto the
> image
> creation tool that causes this?
I suspect your version of U-Boot does not handle files spread across
multiple filesystems (allocation) extends efficiently.
Copying the file makes the copy being layed out in one extend probably.
I am aware of two fixes for U-Boot. I will look them up, and reply again to
this thread.
Regards, Leon
--
Leon Woestenberg
leon@sidebranch.com
T: +31 40 711 42 76
M: +31 6 472 30 372
Sidebranch
Embedded Systems
Eindhoven, The Netherlands
http://www.sidebranch.com
[-- Attachment #2: Type: text/html, Size: 3164 bytes --]
next prev parent reply other threads:[~2019-02-19 17:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 11:20 wic creates ext4 images that read really slow in u-boot Mike Looijmans
2019-02-19 17:13 ` Leon Woestenberg [this message]
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='CAMjhiJjO0+0=_6HOmVM67U0nnbW=iu-FiMTzJBe4ZCvceuguuA@mail.gmail.com' \
--to=leon@sidebranch.com \
--cc=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 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.