Skip to content

Conversation

tschatzl
Copy link
Contributor

@tschatzl tschatzl commented Sep 30, 2025

Hi all,

please review some documentation update why G1 now uses TLS storage to get the current card table base value for the card mark.

TLDR: it's the overall fastest currently available way.

Testing: local compilation, this is just a trivial documentation change.

Thanks,
Thomas


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8368954: G1: Document why G1 uses TLS storage for the current card table reference (Enhancement - P4)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27573/head:pull/27573
$ git checkout pull/27573

Update a local copy of the PR:
$ git checkout pull/27573
$ git pull https://git.openjdk.org/jdk.git pull/27573/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 27573

View PR using the GUI difftool:
$ git pr show -t 27573

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27573.diff

Using Webrev

Link to Webrev Comment

Hi all,

  please review some documentation update why G1 now uses TLS storage to get the current card table base value for the card mark.

TLDR: it's the overall fastest currently available way.

Testing: local compilation, this is just a trivial documentation change.

Thanks,
  Thomas
@bridgekeeper
Copy link

bridgekeeper bot commented Sep 30, 2025

👋 Welcome back tschatzl! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Sep 30, 2025

@tschatzl This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8368954: G1: Document why G1 uses TLS storage for the current card table reference

Reviewed-by: ayang, rcastanedalo, iwalulya

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 8 new commits pushed to the master branch:

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

@openjdk openjdk bot changed the title 8368954 8368954: G1: Document why G1 uses TLS storage for the current card table reference Sep 30, 2025
@openjdk openjdk bot added the hotspot-gc hotspot-gc-dev@openjdk.org label Sep 30, 2025
@openjdk
Copy link

openjdk bot commented Sep 30, 2025

@tschatzl The following label will be automatically applied to this pull request:

  • hotspot-gc

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

@openjdk openjdk bot added the rfr Pull request is ready for review label Sep 30, 2025
@mlbridge
Copy link

mlbridge bot commented Sep 30, 2025

Webrevs

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Sep 30, 2025
Comment on lines 45 to 46
// E.g. embedding an address to that value directly into the code stream similar
// to Serial/Parallel and then loading from that was found to be slower at least
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if I misunderstood this text or not, but Serial/Parallel doesn't embed the "address" into the code stream -- they embed the actual value in the code stream, since the value (card-tabe-base) is constant. G1 can't/doesn't do that, since card-table-base is not constant.

Copy link
Contributor Author

@tschatzl tschatzl Sep 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But G1 can embed the address of the value in the code stream, similar to Serial/Parallel (which embed the actual base address). The emphasis should be on the embedding, not what is embedded.

Copy link
Contributor Author

@tschatzl tschatzl Sep 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe just remove the "an address" to avoid the confusion?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's my misunderstanding then. How about just dropping "similar to Serial/Parallel"? I don't see any benefit of referencing them here.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe just remove the "an address" to avoid the confusion?

I think you need the "address" to connect with the latter "loading from that" -- "that" refers to the "address", doesn't it?

@openjdk openjdk bot removed the ready Pull request is ready to be integrated label Sep 30, 2025
@openjdk openjdk bot added the ready Pull request is ready to be integrated label Sep 30, 2025
@tschatzl
Copy link
Contributor Author

tschatzl commented Oct 1, 2025

Thanks @robcasloz @walulyai @albertnetymk for your reviews
/integrate

@openjdk
Copy link

openjdk bot commented Oct 1, 2025

Going to push as commit 1188ca5.
Since your change was applied there have been 13 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Oct 1, 2025
@openjdk openjdk bot closed this Oct 1, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Oct 1, 2025
@openjdk
Copy link

openjdk bot commented Oct 1, 2025

@tschatzl Pushed as commit 1188ca5.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hotspot-gc hotspot-gc-dev@openjdk.org integrated Pull request has been integrated
Development

Successfully merging this pull request may close these issues.

4 participants