Lock memory by default on a realtime system setup (#1896)

ros-controls · Dec 4, 2024 · dbee650 · dbee650
1 parent 3052b58
commit dbee650
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/controller_manager/doc/userdoc.rst b/controller_manager/doc/userdoc.rst
@@ -325,7 +325,7 @@ The controller_manager can be launched with the ros2_control_node executable. Th
 
 The ros2_control_node executable uses the following parameters from the ``controller_manager`` node:
 
-lock_memory (optional; bool; default: false)
+lock_memory (optional; bool; default: false for a non-realtime kernel, true for a realtime kernel)
   Locks the memory of the ``controller_manager`` node at startup to physical RAM in order to avoid page faults
   and to prevent the node from being swapped out to disk.
   Find more information about the setup for memory locking in the following link : `How to set ulimit values <https://access.redhat.com/solutions/61334>`_

diff --git a/controller_manager/src/ros2_control_node.cpp b/controller_manager/src/ros2_control_node.cpp
@@ -59,7 +59,8 @@ int main(int argc, char ** argv)
 
   const bool use_sim_time = cm->get_parameter_or("use_sim_time", false);
 
-  const bool lock_memory = cm->get_parameter_or<bool>("lock_memory", false);
+  const bool has_realtime = realtime_tools::has_realtime_kernel();
+  const bool lock_memory = cm->get_parameter_or<bool>("lock_memory", has_realtime);
   std::string message;
   if (lock_memory && !realtime_tools::lock_memory(message))
   {