|
|
|
|
|
|
by JoshTriplett
3636 days ago
|
|
|
Signals seem like the kind of thing one would inflict on userspace after having had to deal with interrupts in the kernel, yes. "Share in my pain, userspace programmers!" A standard mechanism needs to exist to send a message to an arbitrary process for things like "please gracefully terminate", but I think the ideal interface looks like a combination of 1) signalfd (minus some of the legacy signal-specific bits), for any signals the process can handle, and 2) an in-kernel mechanism to SIGKILL, SIGSTOP, or SIGCONT processes, which the process can't do anything about anyway. (And things like SIGWINCH should never have been signals; those should just be a standard message associated with the terminal device itself.) |
|
|