-
- Downloads
make cancellation in all emper variants sound
* Document data races of a future's state. * Get and set a Future's state only through methods. This helps to add possibly needed atomic operations. * Use atomics to get/set cancel and prepare state in IO_SINGLE_URING vaiant * Add more IO debug messages * Use the BPS of Futures with callbacks similar to those of forgotten ones to signal their preparation. The preparation mark the last moment where the Future is used in EMPER and after that the memory can be dropped. ATTENTION: This means not that the used resources of the IO request can be dropped. The kernel may still use a supplied buffer for example. * Fix Future chain cancellation in SubmitActor
Showing
- emper/io/Future.cpp 26 additions, 19 deletionsemper/io/Future.cpp
- emper/io/Future.hpp 177 additions, 48 deletionsemper/io/Future.hpp
- emper/io/IoContext.cpp 17 additions, 15 deletionsemper/io/IoContext.cpp
- emper/io/IoContext.hpp 2 additions, 2 deletionsemper/io/IoContext.hpp
- emper/io/SubmitActor.cpp 3 additions, 1 deletionemper/io/SubmitActor.cpp
- tests/io/CancelFutureTest.cpp 10 additions, 1 deletiontests/io/CancelFutureTest.cpp
Loading
Please register or sign in to comment