-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
linux AIO support #52
Comments
Oh, I think it somehow like windows IOCP. I think we can uniform the interface for |
The linux aio is not yet perfect right now, especially we need to have a io manager for the direct access memory. And there are other solutions pushing forward like io_uring which seems have better performance. windows IOCP implementation is quite easy for the requirement and it's done. |
Yeah, for sled I'm thinking about skipping AIO support initially and just
targeting io_uring for the time being since it's so much nicer to work with
and also so much more performant
…On Fri, Apr 19, 2019, 04:58 Xudong Huang ***@***.***> wrote:
The linux aio is not yet perfect right now, especially we need to have a
io manager for the direct access memory. And there are other solutions
pushing forward like io_uring which seems have better performance.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#52 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AALPRUEOP7HMWTCNMQMNHUTPREYNZANCNFSM4G22W3LQ>
.
|
I don't know if it helps. this id a library here rust-io-uring |
Just read https://www.usenix.org/system/files/fast19-kourtis.pdf and it makes a really compelling case for the combination of stackful coroutines + proper linux AIO (and eventually SPDK support). This is a combination I could actually imagine myself using in sled, where I'm now trying to scale toward a many-core architecture, but don't want to pay the various ergonomic costs associated with the popular async stuff in the rust ecosystem right now.
https://github.com/hmwill/tokio-linux-aio may be a nice reference for building linux AIO support for May.
Would you be interested in having AIO support in May directly, or do you see this as something better implemented in a separate library? Very curious about this :)
The text was updated successfully, but these errors were encountered: