@@ -30,7 +30,7 @@ For this example, we will be configuring the main thread scheduling policy of th
3030where the node is spinning. In this case, the middleware threads will not inherit these settings
3131because they are created after the scheduling configuration.
3232
33- ## Using SCHED_OTHER scheduling policy
33+ #### Using SCHED_OTHER scheduling policy
3434
3535We start with the default settings, which means we don't configure the main thread scheduling
3636policy and priority. In Linux, by default, the ` SCHED_OTHER ` scheduling policy is used. Since,
@@ -43,7 +43,7 @@ $ ros2 run minimal_scheduling minimal_scheduling_main_thread
4343
4444<script id =" asciicast-gxZvQuyvNZQR1Y75nFUCq7GQ8 " src =" https://asciinema.org/a/gxZvQuyvNZQR1Y75nFUCq7GQ8.js " async ></script >
4545
46- ## Using SCHED_FIFO scheduling policy
46+ #### Using SCHED_FIFO scheduling policy
4747
4848Now we run the same example but using the ` SCHED_FIFO ` scheduling policy and setting a priority
4949of 80.
@@ -79,7 +79,7 @@ each thread scheduling individually, allowing to set a priority different creato
7979
8080<script id =" asciicast-XzlFpNwZKw0hea9vhfKFCMgj4 " src =" https://asciinema.org/a/XzlFpNwZKw0hea9vhfKFCMgj4.js " async ></script >
8181
82- ## Using SCHED_RR scheduling policy
82+ #### Using SCHED_RR scheduling policy
8383
8484Now we run the same example but using the ` SCHED_RR ` scheduling policy and setting a priority
8585of 80. We expect to see the same results as in the previous case.
0 commit comments