[roll] Roll fuchsia [kernel][vm] Synchronize reclamation with aging Adds a mechanism for reclamation, via the PeekReclaim method, to synchronize with any pending aging events. This means that if there is aging that should happen, PeekReclaim will wait for it to complete before insisting there are no pages available. This can resolve a scenario where we falsely OOM on a heavily loaded system. Supporting this synchronization method required the timeout logic that was implicitly in the MruThread to be made available to generally query if aging should happen. To make this simpler the aging_event_ was re-defined to what it is actually used for, just indicating an active ratio trigger, and methods and call sites around this trigger were cleaned up to acknowledge this specialization. Run-All-Tests: True Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1031012 Original-Revision: e7ada37ecfa5599a9004805ad143e5de750b8f5c GitOrigin-RevId: 787fa7fcf379e03e4f4b8dd832b74416205b2f16 Change-Id: Ie36367cfb8fe75c6f344e48d612793c33acf91da
This repository contains Fuchsia's Global Integration manifest files.
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.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.