<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Feb 18, 2014, at 6:07 PM, <a href="mailto:exarkun@twistedmatrix.com">exarkun@twistedmatrix.com</a> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On 18 Feb, 07:29 pm, <a href="mailto:glyph@twistedmatrix.com">glyph@twistedmatrix.com</a> wrote:<br><blockquote type="cite"><br>On Feb 15, 2014, at 5:32 PM, <a href="mailto:exarkun@twistedmatrix.com">exarkun@twistedmatrix.com</a> wrote:<br><blockquote type="cite">On 15 Feb, 07:58 pm, <a href="mailto:glyph@twistedmatrix.com">glyph@twistedmatrix.com</a> wrote:<br><blockquote type="cite"><br>The one thing that confused me was that the sample program appeared to be running the program only once a second, and waiting for it to complete before running it again.<br></blockquote><br>I think it's more like 81 processes once a second and *not* waiting for them to complete before starting over. Notice the lack of yields in key places. I suspect inlineCallbacks has gradually eaten out the part of your brain that recognizes that keyword. ;)<br></blockquote><br>I sort of noted this on the ticket, but I think the idea of using KQueue to address this would be great. Is there a similar thing we might be able to do on Linux to get rid of the dependence on a SIGCHLD handler?<br></blockquote><br>Not that I know of. As far as I know Linux is missing good child process event notification support.<br></blockquote></div><br><div>Wait... what about... signalfd?!</div><div><br></div><div>Lots of mentions of SIGCHLD here:</div><div><br></div><div><<a href="http://linux.die.net/man/2/signalfd">http://linux.die.net/man/2/signalfd</a>></div><div><br></div><div>-g</div></body></html>