Hacker News new | past | comments | ask | show | jobs | submit login

BeOS is not a realtime OS. It's scheduler is just optimized for multimedia tasks and GUI responsiveness. The popular realtime OS from the BeOS glory days days was QNX (and it's Photon graphical interface), but it certainly never "felt" faster than BeOS on the same hardware.



BeOS was definitely a real time OS. BeOS had two scheduling classes, threads with a priority level between 1-99 were time shared threads where the quantum was proportional with 2^priority_level, threads with a priority level between 100 and 120 were real time threads, they could preempt any other thread, including any kernel thread, they were locked to a CPU and never preempted. And when a real time thread was created, it preempted any time shared thread immediately, the scheduler run at creation, it wasn't only added to a scheduling queue like time shared threads.

QNX is a still very popular realtime OS in the embedded world today. Btw, the OS run by the BlackBerry devices is QNX. Usually you'll find QNX in control systems like avionics.


From what I've read, "realtime" threads with higher priority could preempt other realtime threads, meaning they could be pre-empted.


That's true of every other RTOS out there, in fact, it's required to be this way in order to provide deterministic latency.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: