<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Usage of timerfd_create and signalfd prevent porting to non-linux platforms" href="https://bugs.freedesktop.org/show_bug.cgi?id=91799#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Usage of timerfd_create and signalfd prevent porting to non-linux platforms" href="https://bugs.freedesktop.org/show_bug.cgi?id=91799">bug 91799</a> from <a class="email" href="mailto:daniel@fooishbar.org" title="Daniel Stone <daniel@fooishbar.org>"> Daniel Stone</a> <pre>(In reply to Alexander von Gluck from <a href="show_bug.cgi?id=91799#c1">comment #1</a>) > <a href="https://ldpreload.com/blog/signalfd-is-useless">https://ldpreload.com/blog/signalfd-is-useless</a> a pretty good article on > signalfd. See the note at the end: 'So my claim that there’s a better alternative to signalfd is wrong [...]'. > The solution for this usage is to just spin up a pthread to grab > signals. Yeah, introducing threads just delivers a whole series of other problems, particularly as the pthread API is so fragile and broken. My preferred solution would be something similar to XCB's libpthread-stubs, where we allow other platforms to provide an API similar to that of signalfd - an FD to add to our existing event loop dispatch which notifies us of signals - providing their own implementation, which could use pthreads. But going to pthreads makes the lives of a lot of users measurably worse, and going to #ifdefs makes the lives of most developers measurably worse.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>