SimpleEventBuilder/testing/is_epoll_really_thsafe
MasterRoby3 ac02149c6d Fully implemented multi_th test and got test results 2023-08-27 21:40:36 +02:00
..
ev_builder.out Fully implemented multi_th test and got test results 2023-08-27 21:40:36 +02:00
event_builder_epoll.cxx Fully implemented multi_th test and got test results 2023-08-27 21:40:36 +02:00
exec_order_test.sh Fully implemented multi_th test and got test results 2023-08-27 21:40:36 +02:00
prov.out Fully implemented multi_th test and got test results 2023-08-27 21:40:36 +02:00
provider.cxx Fully implemented multi_th test and got test results 2023-08-27 21:40:36 +02:00
readme.md Added epoll test on thread safety 2023-08-27 16:18:17 +02:00
res.txt Fully implemented multi_th test and got test results 2023-08-27 21:40:36 +02:00

readme.md

Is epoll really thread safe?

Motivation

Scope of this test is simply to verify that TCP communication with epoll doesen't mix data. In particular, it's important to verify that if one big chunk is sent, the TCP protocol doesen't split it into different events for level triggered epoll (ofc it's gonna be splitted due to buf size).

The important thing is that if I send 1MB of data, it doesen't wake up 2 threads listening to the same fd just because TCP split the package (afaik that shouln't happen, but it's always better to verify, since epoll() is fundamentally broken)