3 ms·
Most of this article seems like mere unfamiliarity with how interrupts are generally processed. The point is you're just getting a flag indicating that you need
by mindslight 2y ago
Most of this article seems like mere unfamiliarity with how interrupts are generally processed. The point is you're just getting a flag indicating that you need to poll. You do the least possible in the interrupt handler so the rest of your program is disrupted as little as possible. The advantages of this aren't so super necessary when you're already event driven using select() and its descendants. But it's also not terribly hard to work into that paradigm, awkwardness of the loopback fd pattern in directly-written-C not withstanding.
System calls returning early with EINTR is the exact example from Worse is Better, so that's been been debated to death.
And FWIW it seems like SA_SIGINFO itself is more of the problem, especially if (when?) there isn't a good way to poll that information elsewhere.