You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apparently can do 1.7M 4k IOPS per CPU core. As PCIe maxes out at a theoretical 2M 4k IOPS due to PCIe bus latency, that's pretty great for O_DIRECT i/o. It may even be worth deploying this for the synchronous implementation on Linux, though synchronous reads can reach 4M 4k IOPS/core on Linux.
This actually should be folded into a new nonblocking_file_handle which implements non-blocking synchronous i/o, and coroutinised resumable i/o. This would allow us to drop async_file_handle.
Apparently can do 1.7M 4k IOPS per CPU core. As PCIe maxes out at a theoretical 2M 4k IOPS due to PCIe bus latency, that's pretty great for O_DIRECT i/o. It may even be worth deploying this for the synchronous implementation on Linux, though synchronous reads can reach 4M 4k IOPS/core on Linux.
https://lwn.net/Articles/776703/
Example of use: http://git.kernel.dk/cgit/fio/plain/t/io_uring.c
The text was updated successfully, but these errors were encountered: