| commit | 8e7250d9179664181292e957a9a0132767a0ff2b | [log] [tgz] |
|---|---|---|
| author | Nick Maniscalco <maniscalco@fuchsia.infra.roller.google.com> | Wed Apr 09 13:40:43 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Apr 09 13:42:17 2025 -0700 |
| tree | fcb04c096bab8dadf13218ad1fbeb5703f9e9989 | |
| parent | c585d338c8985ca6a447de34a5cf62b15a3701ba [diff] |
[roll] Roll fuchsia [kernel][futex] Improve futex performance of shared processes Improve futex performance of shared processes by giving FutexContext's HashTable more buckets. We've observed that shared processes (think Starnix) tend to have between 1000 and 2000 active futexes. Furthermore, products that use shared processes tend to perform many futex operations per second. Prior to this change, the hash table backing those active futexes had only 37 buckets, which meant that the average futex operation had to walk about 27 elements of a linked list (pointer chasing without cache locality). By giving shared processes more buckets (1031) we bring that number down to 1 or 2. Memory usage of a group of shared processes increases by a small amount (about 8KiB), but keep in mind that the increase is per group, rather than per process since all members of a group share the same FutexContext. No impact to regular (non-shared) processes. See https://fxbug.dev/382492390 for more details and analysis. Original-Bug: 382492390 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1105015 Original-Revision: dc99b5f3eeb40446d9f3f0731313896364b44993 GitOrigin-RevId: 9456a46c2b8831a47448406355f772f63d6b8003 Change-Id: I9f860acf78ed17624884e2a3bfaaf99c24f781fe
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 in one of the communication channels documented at get involved.
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.