Tracking issues of Completion Based IO

[Xuanwo]

OpenDAL wants REAL async fs io for long time:

• feat: Implement io_uring support via tokio_uring #1480
• Add support completion based IO #489
• Implement io_uring support to replace tokio-fs #477
• Async fs support #19

None of them have become reality. Currently, OpenDAL's services-fs is powered by tokio-fs, which simply spawns I/O to the thread pool.

Plan

This issue tracks the progress of Completion Based IO. Our goal is to allow users to use different runtime they want freely.

For greater clarity: Each runtime will have separate services, such as services-compfs for compio. Users can enable and switch between runtimes by modifying these services. Each service will independently manage the specific aspects of its corresponding runtime.

For example:

let op = Operator::via_map(Scheme::Compfs, map)?;
let bs = op.read("path/to/file").await?;

Runtimes

• Tracking issue for services-compfs #4518
• Add native support for monoio project #4552
• nuclei
• tokio_uring