From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC][PATCH] block: Enable block cache by default
Date: Fri, 18 May 2018 11:22:53 +0200 [thread overview]
Message-ID: <20180518092253.24255-1-marex@denx.de> (raw)
The recent ext4 cache discussion would indicate that the block cache
is a desired feature, yet hidden and not enabled most of the time.
Enable the block cache by default since it provides significant block
device access performance improvement and if there are some users who
cannot enable it ie. due to size limitations, those should disable it
explicitly in their board config.
Signed-off-by: Marek Vasut <marex@denx.de>
Cc: Simon Glass <sjg@chromium.org>
Cc: Michal Simek <michal.simek@xilinx.com>
Cc: Tom Rini <trini@konsulko.com>
---
drivers/block/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/block/Kconfig b/drivers/block/Kconfig
index 15fd1bcb2b..832d626bd4 100644
--- a/drivers/block/Kconfig
+++ b/drivers/block/Kconfig
@@ -29,7 +29,7 @@ config SPL_BLK
config BLOCK_CACHE
bool "Use block device cache"
- default n
+ default y
help
This option enables a disk-block cache for all block devices.
This is most useful when accessing filesystems under U-Boot since
--
2.16.2
next reply other threads:[~2018-05-18 9:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 9:22 Marek Vasut [this message]
2018-05-19 14:36 ` [U-Boot] [RFC][PATCH] block: Enable block cache by default Simon Glass
2018-05-19 18:20 ` Marek Vasut
2018-05-19 20:50 ` Tom Rini
2018-05-19 21:39 ` Marek Vasut
2018-05-19 22:29 ` Tom Rini
2018-05-19 23:39 ` Marek Vasut
2018-05-21 1:48 ` Tom Rini
2018-05-21 2:17 ` Marek Vasut
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=20180518092253.24255-1-marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/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.