On Tue, 15 Sep 2009, Eric Paris wrote: > > I don't see what's gained using netlink. I'm personally not a big believer in netlink. What's the point, really? If you are sending datagrams back-and-forth, go wild. But if it's more structured than that, netlink has no actual upsides as far as I can tell. Same goes for sockets in this case, actually. What's the upside? I'll throw out a couple of upsides of actual system calls, people can feel free to comment: - things like 'strace' _work_ and the traces make sense, and you generally see what the app is trying to do from the traces (sure, it takes some time for strace to learn new system calls, but even when it only gives a system call number, it's never any worse than some "made-up packet interface". - if you have a system call definition, it tends to be a much stricter interface than "let's send some packets around with a network interface". - No unnecessary infrastructure. That said, maybe the netlink/socket people can argue for their standpoints. (And btw, I still want to know what's so wonderful about fanotify that we would actually want yet-another-filesystem-notification-interface. So I'm not sayying that I'll take a system call interface. I just don't think that hiding interfaces behind some random packet interface is at all any better) Linus -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
