Skip to content

U
U-Boot.Mirror

OS / U-Boot.Mirror

通知 1
Star 0
Fork 0
U
U-Boot.Mirror

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 28 1月, 2017 1 次提交
  3. 28 12月, 2016 1 次提交
  5. 02 10月, 2016 2 次提交
  7. 17 5月, 2016 12 次提交
  9. 15 4月, 2016 1 次提交
  11. 02 4月, 2016 1 次提交
    • E
      drivers: block: add block device cache · e40cf34a
      由 Eric Nelson 提交于 
      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 fc0fc50f.

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: NEric Nelson <eric@nelint.com>
      e40cf34a
  13. 16 3月, 2016 1 次提交
  15. 15 3月, 2016 7 次提交
  17. 20 1月, 2016 1 次提交
    • E
      mmc: emmc and hw partitions partition table id bugfix. · 99e7fc8a
      由 Erik Tideman 提交于 
      On bootup the emmc's hw partition is always set to 0 and the partition
table is read from it. When switching to another hw partition the
partition table's id is not updated but instead the old one from
hw partition 0 is used. If there is no partition table on hw partition 0
then the code will terminate and return error even if the desired hw
partition contains a perfectly fine partition table. This fix updates
the partition table struct to correspond to the specified hw partition
before testing if the partition table is valid or not.
Signed-off-by: NErik Tideman <erik.tideman@faltcom.se>
Reviewed-by: NTom Rini <trini@konsulko.com>
[trini: Squash the patch that corrected whitespace in the original into
this one, wrap with HAVE_BLOCK_DEVICE test]
Signed-off-by: NTom Rini <trini@konsulko.com>
      99e7fc8a
  19. 13 11月, 2015 1 次提交
  21. 25 10月, 2015 2 次提交
  23. 25 10月, 2014 1 次提交
  25. 25 9月, 2014 1 次提交
  27. 22 7月, 2014 1 次提交
  29. 24 6月, 2014 1 次提交
    • S
      sandbox: restore ability to access host fs through standard commands · 4d907025
      由 Stephen Warren 提交于 
      Commit 95fac6ab "sandbox: Use os functions to read host device tree"
removed the ability for get_device_and_partition() to handle the "host"
device type, and redirect accesses to it to the host filesystem. This
broke some unit tests that use this feature. So, revert that change. The
code added back by this patch is slightly different to pacify checkpatch.

However, we're then left with "host" being both:
- A pseudo device that accesses the hosts real filesystem.
- An emulated block device, which accesses "sectors" inside a file stored
  on the host.

In order to resolve this discrepancy, rename the pseudo device from host
to hostfs, and adjust the unit-tests for this change.

The "help sb" output is modified to reflect this rename, and state where
the host and hostfs devices should be used.
Signed-off-by: NStephen Warren <swarren@nvidia.com>
Tested-by: NJosh Wu <josh.wu@atmel.com>
Acked-by: NSimon Glass <sjg@chromium.org>
Tested-by: NSimon Glass <sjg@chromium.org>
      4d907025
  31. 12 6月, 2014 1 次提交
    • S
      disk: default to HW partition 0 if not specified · ecdd57e2
      由 Stephen Warren 提交于 
      Currently, get_device()/get_dev_hwpart() for MMC devices does not select
an explicit HW partition unless the user explicitly requests one, i.e. by
requesting device "mmc 0.0" rather than just "mmc 0". I think it makes
more sense if the default is to select HW partition 0 (main data area)
if the user didn't request a specific partition. Otherwise, the following
happens, which feels wrong:

Select HW partition 1 (boot0):
mmc dev 0 1

Attempts to access SW partition 1 on HW partition 1 (boot0), rather than
SW partition 1 on HW partition 0 (main data area):
ls mmc 0:1 /

With this patch, the second command above re-selects the main data area.

Many device types don't support HW partitions at all, so if HW partition
0 is selected (either explicitly or as the default) and there's no
select_hwpart function, we simply skip attempting to select a HW
partition.

Some MMC devices (i.e. SD cards) don't support HW partitions. However,
this patch still works, since mmc_start_init() sets the current
partition number to 0, and mmc_select_hwpart() succeeds if the requested
partition is already selected.
Signed-off-by: NStephen Warren <swarren@nvidia.com>
Acked-by: NPantelis Antoniou <panto@antoniou-consulting.com>
      ecdd57e2
  33. 23 5月, 2014 2 次提交
  35. 18 3月, 2014 1 次提交
    • S
      sandbox: Use os functions to read host device tree · 95fac6ab
      由 Simon Glass 提交于 
      At present we use U-Boot's filesystem layer to read the sandbox device tree,
but this is problematic since it relies on a temporary feauture added
there. Since we plan to implement proper block layer support for sandbox,
change this code to use the os layer functions instead. Also use the new
fdt_create_empty_tree() instead of our own code.
Signed-off-by: NSimon Glass <sjg@chromium.org>
      95fac6ab
  37. 09 1月, 2014 1 次提交
  39. 24 7月, 2013 1 次提交