summaryrefslogtreecommitdiff
path: root/cmd/lzmadec.c
diff options
context:
space:
mode:
authorEric Nelson <eric@nelint.com>2016-03-28 10:05:44 -0700
committerTom Rini <trini@konsulko.com>2016-04-01 17:18:27 -0400
commite40cf34a29f1b248643731a11fb1c6f0520d016c (patch)
tree2970c8fdbf0d35135f1d2eddd238372c20ac65f5 /cmd/lzmadec.c
parente721e98125ebaad71bc7d19287ce54c337f59154 (diff)
downloadu-boot-imx-e40cf34a29f1b248643731a11fb1c6f0520d016c.zip
u-boot-imx-e40cf34a29f1b248643731a11fb1c6f0520d016c.tar.gz
u-boot-imx-e40cf34a29f1b248643731a11fb1c6f0520d016c.tar.bz2
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. The cache is implemented through a minimal list (block_cache) maintained in most-recently-used order and count of the current number of entries (cache_count). It uses a maximum block count setting to prevent copies of large block reads and an upper bound on the number of cached areas. The maximum number of entries in the cache defaults to 32 and the maximum number of blocks per cache entry has a default of 2, which has shown to produce the best results on testing of ext4 and FAT filesystems. The 'blkcache' command (enabled through CONFIG_CMD_BLOCK_CACHE) allows changing these values and can be used to tune for a particular filesystem layout. Signed-off-by: Eric Nelson <eric@nelint.com>
Diffstat (limited to 'cmd/lzmadec.c')
0 files changed, 0 insertions, 0 deletions