JDK-8181196 : Update all JVM NUMA prototypes to use the new NUMA API version 2
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 8,9,10
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • OS: linux
  • CPU: generic
  • Submitted: 2017-05-29
  • Updated: 2019-02-11
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-8181055 - PPC64: "mbind: Invalid argument" still seen after 8175813
Relates :  
JDK-8175813 - PPC64: "mbind: Invalid argument" when -XX:+UseNUMA is used
Description
From Volker's comment in [1]: "[W]e still use the NUMA version 1 function prototypes (e.g."numa_node_to_cpus(int node, unsigned long *buffer, int buffer_len)" instead of "numa_node_to_cpus(int node, struct bitmask *mask)", but also "numa_interleave_memory()" and maybe others). I think we should switch all prototypes to the new NUMA version 2 interface"

[1] http://mail.openjdk.java.net/pipermail/hotspot-dev/2017-April/026682.html
Comments
[~gromero]: can you check whether JDK-8213827 is as suggested, ie. changes the code to preferentially use the v2 interface? Also, this CR suggests to *switch* the API - so would it be possible to drop support for the v1 interface? How old is that and are there platforms which do not support the v2 interface - do you happen to know?
14-01-2019