huh, interesting. As far as I can tell the main advantage this has over IOCP is that you can get one completion for multiple read requests.
Looks like they took a lot of the concepts from Winsock RIO and applied them to file I/O. Which is fascinating because with network traffic you can't predict packet boundaries and thus your I/O rate can be unpredictable. RIO helps you get the notification rate under control, which can help if your packet rate is very high.
With files, I would think you can control the rate at which you request data, as well as the memory you allocate for it.
The other thing it saves just like RIO is the overhead of locking/unlocking buffers by preregistering them. Is that the main reason for this API then ?
I would be very interested to hear from people who have actually run into limits with overlapped file reads and are therefore excited about IoRings
https://windows-internals.com/i-o-rings-when-one-i-o-operati...