-
Notifications
You must be signed in to change notification settings - Fork 304
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
Try using SCHED_FIFO on any kernel #1142
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #1142 +/- ##
=======================================
Coverage 31.62% 31.63%
=======================================
Files 94 94
Lines 10838 10836 -2
Branches 7419 7419
=======================================
Hits 3428 3428
+ Misses 804 802 -2
Partials 6606 6606
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
LGTM
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.
🎉❣️
A while back, we did some deeper investigation of cycle-time effects of different kernel / scheduling setups (https://github.com/UniversalRobots/Universal_Robots_ROS_Driver/blob/60f08359f6484d1671e12bab6e01fc49eb0fadc8/ur_robot_driver/doc/real_time_benchmarking.md).
Based on this, using
SCHED_FIFO
is beneficial on any system, not only real-time kernels. Thus, I suggest alwats trying FIFO scheduling in the CM.I've swapped the user setup before the kernel setup in the userdocs for two reasons:
SCHED_FIFO
.