http://bugs.winehq.org/show_bug.cgi?id=58704
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Zeb Figura z.figura12@gmail.com --- I don't think Wine is going to get anything out of io_uring.
There's not anything in the way of batching we do; for anything interesting one win32 syscall is going to translate to one POSIX syscall.
Nor do we do anything interesting that's asynchronous. Win32 I/O is of course asynchronous by nature, but in a way that requires manual handling; we can't easily implement async win32 I/O on top of async Linux I/O.
And even we could, there's two kinds of I/O we do: regular file I/O, which can often skip a server call but is by nature synchronous, and non-regular file I/O, which is asynchronous but also needs to go through the server to signal completion (and sometimes other things). The server RPC is going to dwarf whatever time io_uring might theoretically save.
If I/O is a bottleneck—and I haven't yet seen an application where it actually *is*—then we'll need to address it in other ways.