|
@withoutboats | |||||
|
For the last month and a half or so I’ve been looking at integrating io_uring into Rusts async ecosystem. Here’s the first step boats.gitlab.io/blog/post/iou/
|
||||||
|
||||||
|
Saoirse Shipwreckt
@withoutboats
|
8. stu |
|
This library provides an idiomatic Rust interface to io_uring, written on top of Jens Axboe’s liburing github.com/withoutboats/i…
|
||
|
|
||
|
Saoirse Shipwreckt
@withoutboats
|
8. stu |
|
It’s not 100% safe and it doesn’t have futures support in it, but it provides an API anyone could use to build that layer
|
||
|
|
||
|
Samuel Williams
@ioquatix
|
9. stu |
|
What was your experience working with liburing? Does it add much overhead vs working with the syscalls directly?
|
||
|
|
||
|
Ivan Prisyazhnyy
@JohnKoepi
|
9. stu |
|
It doesn’t add overhead. It contains helpers for managing data returned by io_uring syscalls.
|
||
|
|
||
|
Lorenzo Gabriele
@lorenzoglorenzo
|
11. stu |
|
Did you benchmark it? Do you know hwo it compares with epoll based solution?
I was playing to do the same exact same thing for @scala_native
|
||
|
|
||