YoSTEALTH

There is no need to use `preadv2(..., RWF_NOWAIT)` if you are using `io_uring` as this is already implemented/improved in `io_uring`. https://github.com/axboe/liburing/issues/280#issuecomment-761619799

https://pypi.org/project/liburing/ https://github.com/YoSTEALTH/liburing

It is using CFFI https://github.com/YoSTEALTH/Liburing/blob/master/builder.py I went with Unlicense because SQLite also uses it https://www.sqlite.org/copyright.html and its mostly in everything out there. I am sure SQLite is used in Germany...

For the next release if i change it to CC0 You are happy with that? https://choosealicense.com/licenses/cc0-1.0/

Sure, i can look into it. I am not sure if io_uring is designed to work on 32bit, will have to find out.

> Does Liburing work on 32bit? "Yes, the ABI is designed as such that there are on differences between 32 and 64-bit." Jens Axboe

I am looking at setting the current minimum Linux required to be `5.6` Just because there are so many features missing... like `IORING_OP_SEND|RECV` was added in `5.6` also `IORING_OP_EPOLL_CTL`. `IORING_OP_ACCEPT`...

> This looks like a nice reference on io_uring: https://unixism.net/loti/index.html Its nice to have documentation finally, should help clear out a lot of confusion.

@njsmith have you install liburing python directly from github? its newer then the one on pypy. I haven't used musl to comment on it atm. For me `io_uring_prep_recv` doesn't work,...

Python's `socket` class doesn't work nice with `io_uring` there is some kind of internal conflict with `socket.setblocking` method. Also some of `io_uring` non-blocking features are disabled by the class as...