| commit | 64f1adf7a30423d572b9bd5999f0f58ee8481a26 | [log] [tgz] |
|---|---|---|
| author | David Worsham <dworsham@fuchsia.infra.roller.google.com> | Fri Oct 13 01:34:06 2023 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Oct 12 18:36:13 2023 -0700 |
| tree | c74823405d984f32e86db65cb119b208041357ed | |
| parent | 27e582190cda5a2b42f9a6d79b8b719afc5fdf6f [diff] |
[roll] Roll fuchsia [kernel][vm] Periodically yield VMO lock Periodically yielding the lock during overlapping zx_vmo_read and zx_vmo_write operations should have no impact on correctness, because these operations already yield the lock when a page fault occurs. When interleaving short-running operations with other long-running operations, yielding the lock this way should allow the short-running operations to complete sooner. This has an overall positive impact on latency and system utilization, especially when the system is under load. To avoid slowing down the uncontested case, we only drop the lock when the lock is confirmed to be contested (at least one other thread is yielding/blocking on it). Original-Bug: 118073 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/906462 Original-Revision: b9d1279825224cfc9de2a8b6e7a4383e8bb7c798 GitOrigin-RevId: 453edccaa7466a2fb8753f15e6594e5826b6502d Change-Id: I0fa60f46fc1b0d24d131808a7f5970dbe514dcbd
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.