Re: [PATCH] event-loop: fix blocking timerfd read

2013-10-25 Thread Kristian Høgsberg
On Thu, Oct 17, 2013 at 02:20:31PM +0200, David Herrmann wrote: If we call wl_event_source_check() on a timerfd, our dispatcher will block on the timerfd read(). Avoid calling read() if no epoll-event was reported. Note: The internal tick-count of a timerfd is never decreased. So once we

[PATCH] event-loop: fix blocking timerfd read

2013-10-17 Thread David Herrmann
If we call wl_event_source_check() on a timerfd, our dispatcher will block on the timerfd read(). Avoid calling read() if no epoll-event was reported. Note: The internal tick-count of a timerfd is never decreased. So once we get signaled a read event, a following read() is guaranteed to succeed