-
Enhancement
-
Resolution: Fixed
-
P4
-
11
-
b14
From the very beginning, NMT treats thread stack as virtual memory allocation and tracks them in the same way as virtual memory.
However, it is not the case, pthread library does not dictate how stack is allocated (see the discussion [1] for details)
It should not be hard to pull thread stacks into another tracking list. Matter of fact, it might simplify a few things, as we started doing something special the thread stacks, e.g. figuring out actual stack range in used and where are guard pages.
[1] http://mail.openjdk.java.net/pipermail/hotspot-runtime-dev/2018-June/028407.html
However, it is not the case, pthread library does not dictate how stack is allocated (see the discussion [1] for details)
It should not be hard to pull thread stacks into another tracking list. Matter of fact, it might simplify a few things, as we started doing something special the thread stacks, e.g. figuring out actual stack range in used and where are guard pages.
[1] http://mail.openjdk.java.net/pipermail/hotspot-runtime-dev/2018-June/028407.html
- relates to
-
JDK-8202772 NMT thread stack tracking causes crashes on AIX
- Resolved
-
JDK-8301466 [AIX] Revisit CommittedVirtualMemoryTest
- Resolved