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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add omrthread_get_self_thread_time() #7491
base: master
Are you sure you want to change the base?
Add omrthread_get_self_thread_time() #7491
Changes from all commits
e42e83b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given these existing API functions, what's the real value of adding this function?
If we decide to go ahead with this change, this should use
omrthread_get_self_cpu_time()
andomrthread_get_self_user_time()
instead.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see what you mean. Yeah, I think the best way is to add Linux implementation to
omrthread_get_self_user_time()
so we don't need to add a new function. Then we'll be callingomrthread_get_self_cpu_time()
andomrthread_get_self_user_time()
on the J9 side. @tajila what do you think?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was hoping to avoid calling
getrusage
twice, since we need both cpu and user time. What does the support look like on other platforms, are they separate system calls or can those be bundled as well.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like on Windows and AIX they can be bundled as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we're concerned about making two system calls where one would suffice, I suggest this function should be used by
omrthread_get_self_cpu_time()
andomrthread_get_self_user_time()
to reduce code duplication.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not a good idea because on some platforms
omrthread_get_self_cpu_time
get CPU time directly rather than by adding user time and system time.