| … | |
… | |
| 65 | * of timeouts later :). |
65 | * of timeouts later :). |
| 66 | * h) initially there was a hardcoded limit of 4096 outstanding events. |
66 | * h) initially there was a hardcoded limit of 4096 outstanding events. |
| 67 | * later versions not only bump this to 32k, but also can handle |
67 | * later versions not only bump this to 32k, but also can handle |
| 68 | * an unlimited amount of events, so this only affects the batch size. |
68 | * an unlimited amount of events, so this only affects the batch size. |
| 69 | * i) unlike linux aio, you *can* register more then the limit |
69 | * i) unlike linux aio, you *can* register more then the limit |
| 70 | * of fd events. while early verisons of io_uring signalled an overflow |
70 | * of fd events. while early versions of io_uring signalled an overflow |
| 71 | * and you ended up getting wet. 5.5+ does not do this anymore. |
71 | * and you ended up getting wet. 5.5+ does not do this anymore. |
| 72 | * j) but, oh my! it had exactly the same bugs as the linux aio backend, |
72 | * j) but, oh my! it had exactly the same bugs as the linux aio backend, |
| 73 | * where some undocumented poll combinations just fail. fortunately, |
73 | * where some undocumented poll combinations just fail. fortunately, |
| 74 | * after finally reaching the author, he was more than willing to fix |
74 | * after finally reaching the author, he was more than willing to fix |
| 75 | * this probably in 5.6+. |
75 | * this probably in 5.6+. |
