On 3/8/07, Davide Libenzi <davidel@xmailserver.org> wrote:
The reason for the special function, was not to provide a non-blocking behaviour with zero timeout (that just a side effect), but to read the siginfo. I was all about using read(2) (and v1 used it), but when you have to transfer complex structures over it, it becomes hell. How do you cleanly compat over a f_op->read callback for example?
Make it a netlink socket and fetch your structures using recvmsg(). siginfo_t belongs in ancillary data. The UNIX philosophy is "everything's a file". The Berkeley philosophy is "everything's a socket, except for files, which are feeble mini-sockets". I'd go with the Berkeley crowd here. Cheers, - Michael - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
