From: Mike Looijmans <mike.looijmans@topic.nl>
To: Leon Woestenberg <leon@sidebranch.com>,
Andre McCurdy <armccurdy@gmail.com>
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: Wed, 20 Feb 2019 10:55:20 +0000 [thread overview]
Message-ID: <5d6f25cb-e7fb-8306-5a6e-afe497620b9a@topic.nl> (raw)
In-Reply-To: <CAMjhiJgFxSH3Rz+ot6qAZN1LPF=WmZ1ySt0Y4TSCg0S0m7YsxQ@mail.gmail.com>
>>> I am aware of two fixes for U-Boot. I will look them up, and reply again to this thread.
Browsing through u-boot commits, I found this gem that's disabled by default:
CONFIG_BLOCK_CACHE=y
The commit is this one:
commit e40cf34a29f1b248643731a11fb1c6f0520d016c
Author: Eric Nelson <eric@nelint.com>
Date: Mon Mar 28 10:05:44 2016 -0700
drivers: block: add block device cache
Add a block device cache to speed up repeated reads of block devices by
various filesystems.
This small amount of cache can dramatically speed up filesystem
operations by skipping repeated reads of common areas of a block
device (typically directory structures).
This has shown to have some benefit on FAT filesystem operations of
loading a kernel and RAM disk, but more dramatic benefits on ext4
filesystems when the kernel and/or RAM disk are spread across
multiple extent header structures as described in commit fc0fc50.
...
I'll be giving that a test drive soon...
next prev parent reply other threads:[~2019-02-21 8:56 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
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 [this message]
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=5d6f25cb-e7fb-8306-5a6e-afe497620b9a@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=armccurdy@gmail.com \
--cc=leon@sidebranch.com \
--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