(draft) add per callback group thread isolation - #3247
Draft
skyegalaxy wants to merge 2 commits into
Draft
Conversation
added 2 commits
September 1, 2026 09:23
Signed-off-by: Skyler Medeiros <skye@polymathrobotics.com>
Signed-off-by: Skyler Medeiros <skye@polymathrobotics.com>
skyegalaxy
marked this pull request as draft
September 1, 2026 16:32
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR adds a new prototype API to the callback group events executor, allowing for individual callback groups to be assigned a dedicated worker thread. That group's events will now be routed to a private per CBG-handle events queue instead of the shared deque, decoupling its latency from the rest of the system load.
Dedicated threads can optionally also be given a thread name, scheduling policy, priority and CPU affinity (linux only)
Example usage:
if your platform doesn't offer CPU pinning / affinity / scheduling policy features, callbacks can still be isolated like so, without passing in a
ThreadOptions:Fixes # (issue)
Is this user-facing behavior change?
Users will now be able to selectively isolate callback groups to their own dedicated thread, and configure the thread options at the posix level if on linux.
Did you use Generative AI?
claude fable 5
Additional Information