| commit | d2ac262ff34fd31f2325551ae76f5d76f119596a | [log] [tgz] |
|---|---|---|
| author | Corey Tabaka <eieio@fuchsia.infra.roller.google.com> | Thu Aug 04 21:34:28 2022 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Aug 04 14:35:56 2022 -0700 |
| tree | 2b540ed343c5f76786f918c82ef0b7bb03025b2f | |
| parent | 7ecac27d3a59ba8e9fb134a9fc13c9c008bb4b47 [diff] |
[roll] Roll fuchsia [kernel][vm] Use CriticalMutex for aspace locks. Mitigate system wide performance impact of threads being preempted while holding arch and vm aspace locks by migrating to CriticalMutex. These locks tend to be widely shared, due to shared memory usage patterns and the common kernel aspace when creating kernel thread stacks. Preemption while holding widely shared, frequently acquired locks can result in cascade delays, particularly when the system is heavily loaded. Prior to this change, CriticalMutex has been updated to use the time limited "timeslice extension" mechanism, instead of straight preempt disable, to reduce the negative impact of long critical sections. Make an additional optimization to the harvest loop to pause harvesting while there are pending access faults for the same aspace, mitigating an issue where the harvest loop succeeds in re-acquiring the aspace lock frequently, even when there are contenders in the mutex spin phase. This change is observed to eliminate access faults blocking while the harvest loop is active on the same aspace. Original-Bug: 71348 Original-Bug: b/234776870 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/504529 Original-Revision: 50bc9593e8ae054e61a46091e84510b642b9e40b GitOrigin-RevId: 12052ffee24e0c0588fdbf1c2a4ae1edd6abc59a Change-Id: I2086d518bfcd20084ba06796d5f45c59295fa1cf
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.