Skip to content
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

runtime: investigate replacing per-thread CLOCK_THREAD_CPUTIME_ID with per-process CLOCK_PROCESS_CPUTIME_ID #65856

Open
prattmic opened this issue Feb 21, 2024 · 0 comments
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone

Comments

@prattmic
Copy link
Member

Linux 6.4+ include https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bcb7ee79029dcaeb09668a4d1489de256829a7cc, which makes CLOCK_PROCESS_CPUTIME_ID prefer to deliver to the thread that caused timer overflow.

We should check whether CLOCK_PROCESS_CPUTIME_ID suffers from the same multi-expiration problem from #35057. I think it probably does, in which case there is nothing to do. But if it doesn't, going back to a single per-process timer would be a nice simplification.

cc @rhysh @golang/runtime

@prattmic prattmic added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Feb 21, 2024
@prattmic prattmic added this to the Backlog milestone Feb 21, 2024
@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
Development

No branches or pull requests

2 participants