3 ms·
Loading a not-present page is typically handled transparently by the OS. Exposing it to the userspace program isn't really useful. I'd suggest to change your e
by moring 4y ago
Loading a not-present page is typically handled transparently by the OS. Exposing it to the userspace program isn't really useful.
I'd suggest to change your example to faulting for a page that doesn't exist in swap either, so a decision has to be made whether to set a flag or e.g. send a signal to the process.
- kazinator 4y agoLoading a not-present page is handled by an exception being signaled, which the operating system has to handle with code. The transparency is a great benefit, which can be attributed to exception handling. > I'd suggest to change your example That is hardly required for my point. > send a signal to the process That's another exception mechanism.