News for hackers. Stuff that matters.
Re:Lord of the Io_uring by cobbzilla on Monday January 06, 2025 @07:17AM (#42609944)
This is a troll, but NT did indeed support async IO via WaitForMultipleObjects in the late 90s, long before Linux had a good async IO story.
Re:Lord of the Io_uring by p_ing on Monday January 06, 2025 @07:24AM (#42609983)
I don't think it's a troll (though not a particularly useful comment); Linux has had no true async story thus far. poll, epoll, et. al. are all synchronous behind-the-scenes.

What Linux still lacks is an OVERLAPPED data structure.

NT has supported async I/O since it's inception. It was a design principle of the kernel -- all I/O operations in the kernel are async'ed.

Re:Lord of the Io_uring by JoshTriplett on Monday January 06, 2025 @07:32AM (#42610034)
I wasn't referring to async I/O. I'm talking about the ability to make system calls using a user/kernel shared memory buffer, without having to enter and exit the kernel. (This is particularly important with all the security mitigations that make kernel entry/exit more expensive.)

https://windows-internals.com/ioring-vs-io_uring-a-compariso...

Re:Lord of the Io_uring by p_ing on Monday January 06, 2025 @08:51AM (#42610528)
Technically Windows has Registered I/O in Windows 8/Server 2012 for networking which provided this functionality. I/O Rings in Windows extended this to other types of I/O, but of course with a separate API.

https://serverframework.com/asynchronousevents/2011/10/windo...

So if we're talking about concepts... NT first, again ;-)