From: Tom Rini <trini@konsulko.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: Thu, 21 Feb 2019 09:33:08 -0500 [thread overview]
Message-ID: <20190221143308.GC12379@bill-the-cat> (raw)
In-Reply-To: <5d6f25cb-e7fb-8306-5a6e-afe497620b9a@topic.nl>
[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]
On Wed, Feb 20, 2019 at 10:55:20AM +0000, Mike Looijmans wrote:
> >>> 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.
For the record, it's not that it's disabled by default but rather to
enable it, you need to enable other "new" frameworks and so forth. And
at least for "legacy" platforms, there's a certain level of pushback
against doing the work required to enable that (as to be honest, it is
more than just enable a few CONFIG options and re-test). A
counter-pushback of "but it enables things that fix some bad performance
problems!" would be really helpful.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2019-02-21 14:33 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
2019-02-21 14:33 ` Tom Rini [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=20190221143308.GC12379@bill-the-cat \
--to=trini@konsulko.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.