What it is
select, poll and epoll all answer which of my connections are ready, but at different costs. select scans bits up to the highest descriptor and is capped at 1024. poll copies and scans every descriptor on each call. epoll registers descriptors once and returns only the ready ones. io_uring submits operations through shared rings, can batch them into one system call and, with SQPOLL, needs none in steady state. This tool counts what each interface forces per ready request and lets you weight those counts.
When to use it
Use it to explain a connection-count limit, to decide whether a poll-based design will survive 10,000 connections, to estimate the memory a thread-per-connection server reserves, or to see how much io_uring batching can save.
Gotchas & limits
The counts follow from the interfaces; the weights are adjustable teaching constants, not nanoseconds, and real cost depends on caches, hardware, kernel version and the application. epoll does not help with regular files. Edge-triggered mode and EPOLLONESHOT change how much work the program does, not only the kernel.