[roll] Roll fuchsia [f2fs] Make StorageBuffer allocation unit configurable

The current |StorageBuffer| manages |VmoBuffer| in single unit.
In this way, even if requests are continuous on the disk, they can fragmented on |VmoBuffer|, which results |fs::BufferedOperationsBuilder| cannot coalesce them.
This CL sets default allocation units to 128, which can cover 512K read operation.

Later, the |StorageBuffer| will allocate the exact size for each operation by exploiting buddy allocator like structure.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/735470
Original-Revision: 5a850c64de7330b4959c5c5d3864d13187d8a28e
GitOrigin-RevId: f9ccc892ecc8c7eb118509970e0695c29cda823a
Change-Id: I35f071cb5ad09b04c8c4afda2180affa03481980
1 file changed
tree: 1c3434d773b0a6a8d6edff08211e2250301bca2e
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
  13. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.