io_uring_cqe.res about liburing HOT 6 CLOSED

Did you advance the CQ ring after reading event 1? I'm guessing not, which means you'll keep seeing the same CQE. Use io_uring_cq_advance() or io_uring_cqe_seen(), whichever is more appropriate for your use case.

from liburing.

I do not have access to those functions.

This does pass https://github.com/YoSTEALTH/Liburing/blob/master/test/file_test.py#L21 but then again the cqe.res content would be wrong (maybe not in this case since both bytearray(5) are same)

from liburing.

Well, you need to advance the CQ ring somehow when you consume events. If the head remains the same, you'll keep reading the same entry.

from liburing.

when i try to write a wrapper for io_uring_cqe_seen https://github.com/YoSTEALTH/Liburing/blob/master/liburing/prep.py#L145 it leads me to having to write a wrapper for everything in https://github.com/axboe/liburing/blob/master/src/include/liburing/barrier.h

I am not a C/Assembly coder.

from liburing.

I was using the wrong tool for the job! I have moved the whole project into using cffi. Now i can access all the liburing functions, no limits, back in action :)

from liburing.

from liburing.