[roll] Roll cobalt-registry [memory] Create an ext4 bucket

Like Fxblob, files served from an ext4 filesystem are loaded in memory
with a userspace pager. This means this memory can be reclaimed by
Zircon under memory pressure.

We prefer to have dedicated buckets for reclaimable memory, as its high
variance during tests and in the field makes it harder to detect
regressions if bundled with non-reclaimable memory.

BUG=489393190

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/cobalt-registry/+/1537840
Privacy-Approval: Alex Pankhurst <pankhurst@google.com>
Original-Revision: 83980fa2524b23026db9954deb47075ef741445d
GitOrigin-RevId: 0f7934fb769c92a17336b97dd62fb162a4284485
Change-Id: If5e61d74871ddb8e5af85d4c5ed7e1e7ba9e8a2b
1 file changed
tree: 9674a7549ad99265417e7df49339d8c6803bc870
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
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 in one of the communication channels documented at get involved.

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.