It's pretty important to understand the timeline here, as the article title can lead the consumer to a lot of wrong conclusions.
* AsynchronousFileChannel was released in jdk7 on 2011-7-28, works by submitting io to a JVM thread pool
* Linux io_uring (AIO) released on 2019-5-5, works at the kernel level
The article's point is that AsynchronousFileChannel does not use io_uring, which makes sense given the API was implemented roughly 8 years previous. Yes, AsynchronousFileChannel is Asynchronous, however, it operates in user space and does not use io_uring.
My observation (and praise) is the JVM implementation is unlikely to break backward compatibility. If io_uring support is desired in Java, you have to jump through a few hoops with the current APIs. Not a big deal in my opinion... if you truely need those few extra percentage points of performance none of this is probably news to you.
* AsynchronousFileChannel was released in jdk7 on 2011-7-28, works by submitting io to a JVM thread pool
* Linux io_uring (AIO) released on 2019-5-5, works at the kernel level
The article's point is that AsynchronousFileChannel does not use io_uring, which makes sense given the API was implemented roughly 8 years previous. Yes, AsynchronousFileChannel is Asynchronous, however, it operates in user space and does not use io_uring.
My observation (and praise) is the JVM implementation is unlikely to break backward compatibility. If io_uring support is desired in Java, you have to jump through a few hoops with the current APIs. Not a big deal in my opinion... if you truely need those few extra percentage points of performance none of this is probably news to you.