Messages in this thread | | | Date | Thu, 17 Oct 2002 10:59:57 -0700 | From | John Gardiner Myers <> | Subject | epoll (was Re: [PATCH] async poll for 2.5) |
| |
Charles 'Buck' Krasic wrote:
>Not exactly. I'm saying that the context in which /dev/epoll is used >(at least originally), is non-blocking socket IO. Anybody who has >worked with that API can tell you there are subtleties, and that if >they're ignored, will certainly lead to pitfalls. These are not the >fault of the /dev/epoll interface. > The particular subtlety I am pointing out is the fault of the currently defined /dev/epoll interface and can be fixed by making a minor change to the /dev/epoll interface.
>I agree if you are talking about AIO as a whole. But epoll is more >limited in its scope, it really relates only to poll()/select not the >whole IO api. > > My objection to the current /dev/epoll API does apply to said "limited scope," it is not dependent on the scope that is "AIO as a whole."
[unhandled content-type:application/x-pkcs7-signature] | |