3 ms·
You would not use io_uring for things like that. Not only will you still use regular file operations on device files for various reasons, should you chose to us
by kennylevinsen 5y ago
You would not use io_uring for things like that. Not only will you still use regular file operations on device files for various reasons, should you chose to use io_uring you would want it to run your entire eventloop and all you I/O rather than single operations here and there. Otherwise it just adds complexity with no benefit.
- throwaway81523 5y agoI don't see the big issue. There is no other way in Linux or Posix to open a file asynchronously (not sure about closing). Dan Bernstein complained about that 20 years ago(?) and io_uring finally fixes it. Before that, runtimes with lightweight processes/threads (Erlang, GHC) used a Posix threadpool to open files in the background. That seems just as messy as using io_uring, which at least keeps everything in the same thread. http://cr.yp.to/unix/asyncdisk.html http://cr.yp.to/unix/asyncdisk.html