Memory Barrier

This is the second part in the series on writing a QNX resource manager in Rust.

Welcome to the first part of a series of posts on how to write a QNX resource manager in Rust.

QNX is billed as a real time operating system, or RTOS.

Along with a new micro-kernel, QNX 8 ships with a new memory manager.

It took a while, but QNX 8 is now free for non-commercial use.

In the post “Virtual Memory”, we saw how each process has its own view of memory, and how processes are isolated from each other.

(If you have not done so already, you may wish to read the previous two posts about memory management, as they contain information that is relevant to following discussion: the basics and virtual memory.)

In the previous post we saw how the memory management unit (MMU) uses page tables to translate virtual addresses into physical ones.

I have recently re-designed the memory manager for QNX 8, getting rid of certain features and improving performance.

I have been a fan of the Qt cross-platform toolkit ever since I first used it in 1999.