Skip to content

We should move from long to byte padding for False Sharing protection #12312

@franz1981

Description

@franz1981
Contributor

We should use byte fields for padding to avoid upcoming false sharing problem in JDK 15+ where field ordering has changed

Activity

normanmaurer

normanmaurer commented on Apr 19, 2022

@normanmaurer
Member

@franz1981 want to give it a spin ?

chrisvest

chrisvest commented on Apr 19, 2022

@chrisvest
Member

In the main branch we've currently removed the padding from InternalThreadLocalMap. There was a TODO that it hadn't been tested if it actually helped or not, so if we add padding back then I think we should also be able to show that it's an improvement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @chrisvest@normanmaurer@franz1981

        Issue actions

          We should move from long to byte padding for False Sharing protection · Issue #12312 · netty/netty