Kernel Recipes 2016 - Who needs a Real-Time Operating System (Not You!) - Steven Rostedt
Why Stack Overflow recommends it
Stack Overflow users link it when answering questions about what makes a kernel real-time or how to build latency-sensitive Linux systems, using it as a trustworthy overview from a kernel developer.
Recommended by 1 people across 1 different months, 2018 to 2020.
What it is
A 41-minute Kernel Recipes 2016 talk by Red Hat's Steven Rostedt explaining what a real-time operating system actually guarantees, namely deterministic response times at the cost of throughput. It covers which requirements truly call for an RTOS and which are better served by a normal OS, at a level meant to be accessible to non-programmers.
What people said
Recommends brokenfoot · 2019-12 · Stack Overflow · on “What makes a kernel/OS real-time?”
Good resource (talk from kernel developer) - Kernel Recipes 2016 - Who needs a Real-Time Operating System (Not You!) - Steven Rostedt [this video]
Cites TBR · 2018-02 · Stack Overflow · on “Recommenden Debian version for developing”
I'd strongly recommend going with Debian 9.3 . The Debian side is not what you need to worry about, it's extremely stable. There are some aspects that you should be aware of, due to a lot of various write-ups being out there. DT overlays get applied in U-Boot (cf. uenv.txt) uenv.txt lives in /boot nowadays, not on the FAT partition If any write-up mentions a 3.8 kernel, disregard it. It will be horribly outdated There are userspace mechanisms now to control pin muxing and pin options Avoid /dev/mem there be many dragons! The question you will need to ask yourself though is which Linux kernel version you will want to run. That will also depend on your actual use case for the Hardware. It's im
Cites Maxim Egorushkin · 2020-03 · Stack Overflow · on “Is it safe to use boost provided shared memory and rt_signal (provided in linux) for realtime system?”
Is it safe to use managed_shared_memory from boost library to minimize unpredictable latency? or should I use mmap() for memory sharing? Manipulating process address space mapping with mmap or brk is an expensive operation [LINK] , so you'd want to minimize the number of times you use mmap . mmap is one source of unpredictable latency. managed_shared_memory uses mmap and provides extra functionality on top of that, which you'd need to implement yourself when using mmap . It probably doesn't matter for performance which one you use since mmap cost is going to dominate. Also Is rt_signal which has channel from SIGRTMIN to SIGRTMAX safe to use? Signals may not be the best choice for IPC because