Messages in this thread |  | | Date | Mon, 19 May 2003 18:02:58 -0700 | From | William Lee Irwin III <> | Subject | Re: Comparing the aio and epoll event frameworks. |
| |
Davide Libenzi wrote: >>> Adding a single shot feature to epoll takes about 5 lines of code, >>> comments included :) You know how many reuqests I had ? Zero, nada.
On Mon, 19 May 2003, Dan Kegel wrote: >> I thought edge triggered epoll *was* single-shot.
On Mon, May 19, 2003 at 05:47:15PM -0700, Davide Libenzi wrote: > For single shot I mean that once you receive one event, you will not > receive more events for that fd if you do not rearm it. Suppose you > receive 1000 bytes of data and you get an event (EPOLLIN). If after 10 > seconds you receive another 1000 bytes, you will receive another event. > This is not single shot.
I think this would be useful for network daemons that would like to fairly schedule responses (i.e. not re-arm until a client on a given fd deserves a turn again). IRC daemons would appear to be a perfect candidate for such. OTOH you may want to wait until someone is writing such a beast so "it will be used" instead of "it is potentially useful".
-- wli - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |