epoll: add EPOLLEXCLUSIVE constant and documentation
commit67217af099363633adf16a15fb0bddbd9d015176
authorEric Wong <sleepy-penguin@bogomips.org>
Sat, 18 Mar 2017 00:56:37 +0000 (18 00:56 +0000)
committerEric Wong <e@80x24.org>
Sat, 18 Mar 2017 00:56:54 +0000 (18 00:56 +0000)
treeebce2e0cea79804149ef4966ca2cb0c76d50adcb
parenta4c4165539c01a2ade5cd7f123295d77733f6624
epoll: add EPOLLEXCLUSIVE constant and documentation

I'm still not convinced this is necessary, but it's in Linux, now,
and maybe some folks will want it.

My position remains:  Never put listen sockets in epoll if
you're using threads; instead, dedicate a thread to doing
nothing but _blocking_ accept4 + epoll_ctl(.. EPOLL_CTL_ADD).

Of course, if you're using something which does not have
native thread support but using multiple processes, then
yes, EPOLLEXCLUSIVE will prevent multiple processes from
turning into a thundering herd.

In other words: I would use this with Perl5, but not with Ruby 1.9+ :P
ext/sleepy_penguin/epoll.c