Home | History | Annotate | Download | only in libevent

Lines Matching full:backend

147   Older versions of Libevent would always got the fastest backend
150 to programmers who wanted to pick a backend explicitly without messing
153 Also, despite our best efforts, not every backend supports every
175 /* There is no backend method that does what we want. */
282 3. Backend-specific and performance improvements.
287 event_add() repeatedly on a single event between trips to the backend's
288 dispatch function, the backend might wind up making unnecessary calls or
289 passing unnecessary data to the kernel. The new backend logic batches up
293 This logic is on for the kqueue backend, and available (but off by
294 default) for the epoll backend. To turn it on for the epoll backend,
322 Unfortunately, the main Windows backend is still select()-based: from
326 backend for better performance with many inactive sockets and better
494 There is now a bufferevents backend that supports IOCP on Windows.