From d16d9e59a1fa262955275cc08cc96a5f91135e86 Mon Sep 17 00:00:00 2001 From: Tobit Flatscher <53856473+2b-t@users.noreply.github.com> Date: Mon, 6 Nov 2023 01:44:37 +0000 Subject: [PATCH] docs: Correct minor formatting mistake --- doc/RealTimeProgramming.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/RealTimeProgramming.md b/doc/RealTimeProgramming.md index c64fe8c..bcabaa5 100644 --- a/doc/RealTimeProgramming.md +++ b/doc/RealTimeProgramming.md @@ -55,7 +55,7 @@ One can find a few developer checklists for real-time programming such as [this] ```c #include - ::mlockall(MCL_CURRENT | MCL_FUTURE) + ::mlockall(MCL_CURRENT | MCL_FUTURE); ``` - Generally real-time processes need to communicate with other non real-time processes. **Do not use standard mutexes (e.g. `std::mutex`) when communicating between threads with different priorities** as this is known to potentially result in [priority inversion](https://en.wikipedia.org/wiki/Priority_inversion): A low-priority task might only run after another task with same or slightly higher priority and therefore block the high-priority task that relies on the low-priority task to complete