Re: epoll reporting events when it hasn't been asked to

[Steven Dake <sdake@mvista.com>]

On Thu, 2004-04-01 at 12:28, Davide Libenzi wrote:
> On Thu, 1 Apr 2004, Ben Mansell wrote:
> 
> > > It is a feature. epoll OR user events with POLLHUP|POLLERR so that even if
> > > the user sets the event mask to zero, it can still know when something
> > > like those abnormal condition happened. Which problem do you see with this?
> > 
> > What should the application do if it gets events that it didn't ask for?
> > If you choose to ignore them, the next time epoll_wait() is called it
> > will return instantly with these same messages, so the app will spin and
> > eat CPU.
> 
> Shouldn't the application handle those exceptional conditions instead of 
> ignoring them?
> 
> 

If an exception occurs (example a socket is disconnected) the socket
should be removed from the fd list.  There is really no point in passing
in an excepted fd.

epoll works just like poll and the expected SUS behavior in this regard.

Thanks
-steve