No, he's referring to something that is not commonly available or used in desktop systems. (I think some Intel CPUs might have it built in, but it's a totally inaccessible feature).
"mlock" is about virtual memory manager "locking" physical pages, so they can't be swapped out to disk.
Here were talking about systems that might not have a disk or even an MMU to implement virtual memory. They might still have dedicated memory protection units, but those aren't necessarily able to support memory virtualization, but just simply to protect memory ranges in safety critical systems.
This is about ability to lock CPU caches (or parts of them, cache line locking) to get something akin to scratchpad memory to ensure deterministic memory access latencies.
For some applications there's a difference whether memory access takes 10 or 100 nanoseconds.
"mlock" is about virtual memory manager "locking" physical pages, so they can't be swapped out to disk.
Here were talking about systems that might not have a disk or even an MMU to implement virtual memory. They might still have dedicated memory protection units, but those aren't necessarily able to support memory virtualization, but just simply to protect memory ranges in safety critical systems.
This is about ability to lock CPU caches (or parts of them, cache line locking) to get something akin to scratchpad memory to ensure deterministic memory access latencies.
For some applications there's a difference whether memory access takes 10 or 100 nanoseconds.