[roll] Roll fuchsia [fxfs] Limit dirty pages when memory is critical

This change installs a new mechanism inside Fxfs so that if memory
pressure is critical, the number of pages that can be dirty in the
pager-backed VMOs is severely limited.

With this change, fxfs no longer OOMs when a client attempts to write
large amounts of data via streams.

Original-Bug: 110000

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/757585
Original-Revision: e8bc7c1905508fc542afa6a9e23b1cc290b343c7
GitOrigin-RevId: 809a9a54c356f901f2d35955bfc80557ced40fc2
Change-Id: Ieb78997eccd237d6ed58968cdf65ebf0abe54b38
1 file changed
tree: a0a0f1efc0a3c40953602520c6add41597e4140c
  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.