-
Notifications
You must be signed in to change notification settings - Fork 299
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
[ros2_control_node] Add option to set the CPU affinity (backport #1852) #1856
Conversation
(cherry picked from commit 98f0795) # Conflicts: # doc/release_notes.rst
Cherry-pick of 98f0795 has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
Needs to be merged after #1850 |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## humble #1856 +/- ##
==========================================
- Coverage 62.50% 62.48% -0.03%
==========================================
Files 108 108
Lines 12160 12166 +6
Branches 8250 8252 +2
==========================================
+ Hits 7601 7602 +1
- Misses 879 883 +4
- Partials 3680 3681 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
|
This pull request is in conflict. Could you fix it @bmagyar @destogl @christophfroehlich @saikishor? |
@mergify rebase |
☑️ Nothing to do
|
This PR adds an option to the ros2_control_node to be able to set the CPU affinity to bind it to a specific CPU Core. By default, this is not enabled, unless it is specifically set
This is an automatic backport of pull request #1852 done by Mergify.