[omworld-jdk] RFR: 8326823: Lilliput: OMWorld: Separate NMT category

[Roman Kennke]

Currently, the OMWorld table uses mtThread NMT category, which seems very wrong. We could instead add it into the mtObjectMonitor or mtSynchronizer categories, but I think it would be more useful to give the table its own category, for measuring overhead and also compare it to ObjectSynchronizer.

Example NMT output would look like:


-           Object Monitors (reserved=1750823568, committed=1750823568)
                           (malloc=1750823568 #8417421) (peak=1958719776 #9416922)
-                  OM World (reserved=151456088, committed=151456088)
                           (malloc=151456088 #8417425) (peak=152173976 #8462293)

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

Commit messages:
 - 8326823: Lilliput: OMWorld: Separate NMT category

Changes: https://git.openjdk.org/lilliput/pull/141/files
 Webrev: https://webrevs.openjdk.org/?repo=lilliput&pr=141&range=00
  Issue: https://bugs.openjdk.org/browse/JDK-8326823
  Stats: 4 lines in 2 files changed: 1 ins; 0 del; 3 mod
  Patch: https://git.openjdk.org/lilliput/pull/141.diff
  Fetch: git fetch https://git.openjdk.org/lilliput.git pull/141/head:pull/141

PR: https://git.openjdk.org/lilliput/pull/141