epoll optimizations
From: Howard Chu
Date: Thu Jan 29 2009 - 10:44:50 EST
Something I tripped over recently, that might be nice to change... HANGUP
events are always reported, and apparently can't be turned off. In
level-triggered mode, if your event loop treats Hangups as lower priority than
read/write events, an outstanding Hangup will continue to be signaled every
time you call epoll_wait() until it's finally disposed of. It would be nice if
Hangups were always oneshot events, regardless of whether the FD was
configured level, edge, or oneshot. Certainly we know that the *cause* of a
Hangup can only happen once on any descriptor, so it makes no sense for it to
be reported more than once.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/