3 ms·
A little bit of a misnomer. You have to mention that IO and driver interaction is still being done in kernel. Just intermediary buffers are remaining MMAPed in
by baybal2 8y ago
A little bit of a misnomer. You have to mention that IO and driver interaction is still being done in kernel. Just intermediary buffers are remaining MMAPed in both kernel and userspace.
That's a step forward from syscalls and excessively frequent context switching, but it is not a real case of userspace driving hardware directly. The later still holds a lot of promise, but it will require hardware to be more smart on its own, and be able to support access concurrency.
Something like that is already being done by hardware supporting virtualisable I/O
- FullyFunctional 8y agoThis is what DSSD did since ~ 2014; drive NVMe directly to the D5 from user app, never incurring a context switch (in fact the D5 was mapping into memory on all the PCIe connected clients). Latency was astonishingly low, dominated by PCIe switches for writes and NAND reads for, eh, reads. EDIT: typo