RFR: 8342444: Shenandoah: Uncommit regions from a separate, STS aware thread [v7]

William Kemper wkemper at openjdk.org
Wed Nov 20 20:31:29 UTC 2024


> Currently, Shenandoah uncommits regions from its control thread. The control thread is responsible for starting GC cycles in a timely fashion. Uncommitting memory from this thread may introduce unwanted delays in the control thread's response to GC pressure.

William Kemper has updated the pull request incrementally with one additional commit since the last revision:

  Restore logging format, show change in committed heap, rather than usage

-------------

Changes:
  - all: https://git.openjdk.org/jdk/pull/22019/files
  - new: https://git.openjdk.org/jdk/pull/22019/files/a00945c2..2cb71140

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jdk&pr=22019&range=06
 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=22019&range=05-06

  Stats: 14 lines in 2 files changed: 10 ins; 3 del; 1 mod
  Patch: https://git.openjdk.org/jdk/pull/22019.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/22019/head:pull/22019

PR: https://git.openjdk.org/jdk/pull/22019


More information about the hotspot-gc-dev mailing list