DylanZA

> You must not share io_uring instances between threads. They are not thread safe, not true - that should work fine. > io_uring _wait_cqe() is busy-waiting and because valgrind serializes...

someone already has submitted this: https://bugs.kde.org/show_bug.cgi?id=428364

If you are concerned about performance it would maybe make more sense to reimplement inline functions natively in Rust? However I'm not sure what the caveats would be with upgrading...

> I think it would be good to error if the user runs spr diff with both the -r and -a option, because that's ambiguous. I did this > And...

It returns the next CQE, but if there is no error then there will be 10 available. If you want a batch you could use `io_uring_peek_batch_cqe` (which actually needs a...

> Hmm.. Could you see in GDB where you are at that point? Maybe make a debug compilation. (I am on vacation and have poor internet, let alone a 128...

fwiw you can replicate the behaviour by setting `RUST_MIN_STACK`. On my 16 core machine I need to use `100000`

SQPOLL doesnt make sense with DEFER_TASKRUN/COOP_TASKRUN or SINGLE_ISSUER as the issuer ends up being the kernel poll thread. you are correct that there seems to be no documentation though :)

> btw, since this function hasn't been in a release yet AFAIK, maybe s/rings/ring? unless there's something i'm missing. just fyi it's been there a long time - so can't...

does https://github.com/torvalds/linux/commit/cbeb47a7b5f003429ded32b1fb3a7108ce5c1b54 help you? you can have a magic user_data and then use the result and flags fields to send your 64 bits? Also I think theres scope to extend...