RTLINUX Test Program :
After adding the RTLINUX patch under openwrt
When running stress-ng for stress testing, it was found that the CPU of rtlinux firmware can reach 50%, and non-rtlinux firmware can reach 100%.
The running command is stress-ng -c 2 --cpu-method pi.
I would like to know more about whether this phenomenon is normal, how to explain it, and if not, how to deal with it.
- RTLINUX
- RTLINUX_1.png (170.16 KiB) Viewed 26914 times
Answer.
In a real-time operating system (RTOS) such as RTLinux, CPU resources are allocated to various tasks, including high-priority real-time tasks and lower-priority non-real-time tasks. When performing stress testing in RTLinux, real-time tasks may occupy part of the CPU resources, causing the stress test program to fail to fully occupy the CPU.
In non-real-time operating systems, CPU resources are usually shared among all tasks in a more balanced manner. Therefore, when stress testing on a non-real-time operating system, stress-ng may occupy large CPU resources and reach 100% CPU utilization.
This behavior is normal in RTLinux. A real-time operating system ensures that high-priority tasks get CPU resources first.
This does not mean that RTLinux performs worse, but rather that it gives different priorities to different tasks.
In summary, while CPU utilization in RTLinux may differ from non-real-time operating systems, this does not mean there is a problem with its performance.
#MA35D1, #RTLINUX
.