thank you for your reply.
I have the same opinion about Linux aio and io_uring. The performance of aio is
not as good and problematic as described, but the use of io_uring may be
limited by the version of the Linux kernel and it makes me hesitant.
There may be very few people who follow up
> 1. "the documentation wrongly claimed that user may modify fd
> and eventsmembers in io watchers when the watcher was stopped." means:
> Can't modify internal members even if I/O watcher has been stopped?
Yes - you have to use ev_io_set or the new ev_io_modify, direct
modification does not
My doubt:
1. "the documentation wrongly claimed that user may modify fd and
eventsmembers in io watchers when the watcher was stopped." means: Can't
modify internal members even if I/O watcher has been stopped?
2. What is the scenario where timerfd checks "Time Jump" cannot
wake up? why a
