2 ms·
Operating system policies are interesting in this regard. Continued correct activity of OS processes is prioritized over user-level activities even where the p
by ncmncm 7y ago
Operating system policies are interesting in this regard.
Continued correct activity of OS processes is prioritized over user-level activities even where the purpose of the system is explicitly the latter. The reasoning seems to be that if the OS can't keep up, it can't maintain the environment that enables user-level stuff to work.
This generates conflict where user-level activities have real-time requirements. It is very, very hard to get your typical OS to leave a process running on a dedicated ("isolated") core and never, ever interrupt it, even given root privileges and boot-time static provisioning. Just store a byte in a file-mapped page, and whoops! get unsynced millisecond pauses while the OS copies it to the disk sector. Oh, and surely you still wanted an interrupt every millisecond to see if any OS resources tied to the core need cleanup, even though it never is asked for OS work.
- jschwartzi 7y agoWhich OS? In QNX this isn't an issue. If you have hard real-time requirements you need to use a Real-Time Operating System.
- ncmncm 7y agoSince when is QNX a typical OS? Most programs need to run on the OS they need to run on, and on the hardware they need to run on. QNX (or other favorite obscurity) most usually is not an option.