Use clock_gettime(CLOCK_MONOTONIC) in omrtime_hires_clock #7065
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Recently, gettimeofday was replaced with
clock_gettime(CLOCK_MONOTONIC_RAW) in omrtime_hires_clock.
This causes a 2-3% regression in startup time.
vDSO support for clock_gettime(CLOCK_MONOTONIC_RAW) was added in Linux
kernel version 5.3: https://bugzilla.kernel.org/show_bug.cgi?id=198961.
The aforementioned regression is seen on Linux kernel versions < 5.3.
Replacing CLOCK_MONOTONIC_RAW with CLOCK_MONOTONIC since it has vDSO
support for older Linux kernel versions, and it also resolves the above
regression in startup time.
Related:
Also, renamed J9TIME_NANO_CLOCK to OMRTIME_NANO_CLOCK.