[roll] Roll fuchsia [blobfs] Support for multiple pager threads.

This commit does not enable multiple pager threads nor does itself
guarantee that we're ready to use multiple threads, but it does provide
a path for turning it on. This will only actually enable multiple
threads for the "new" pager. On the old pager it will allocate extra
resources that will never actually be used.

Adds a mount option for number of paging threads, and uses that to set
the pager threadpool size and allocate the number of required resource
sets for multiple threads to work independently. These resource sets are
then assigned to each pager thread on their first call into the pager by
storing the thread's worker id into a thread local.

Original-Bug: 67659

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/552537
Original-Revision: c3b80be763ab6f1b59c58a75104274432b07bacc
GitOrigin-RevId: 834d7ddedef2dc420b10da46c36da0fb96acc2c4
Change-Id: I5ceb11861b49cf242be891fa957749feae0d2c25
1 file changed
tree: a84188ec63825bfe60960745643bf34fec575e2a
  1. garnet/
  2. infra/
  3. peridot/
  4. third_party/
  5. topaz/
  6. zircon/
  7. firmware
  8. flower
  9. jiri.lock
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. 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 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.