On Fri, 25 Aug 2006 14:18:37 -0500
Michael Halcrow <[email protected]> wrote:
> > - _why_ does it use netlink?
>
> Netlink provides the transport mechanism that would minimize the
> complexity of the implementation, given that we can have multiple
> daemons (one per user). I explored the possibility of using relayfs,
> but that would involve having to introduce control channels and a
> protocol for creating and tearing down channels for the daemons. We do
> not have to worry about any of that with netlink.
I'd have thought that a more appropriate communication mechanism would be
something which uses a file descriptor: a pipe, or a /dev node or whatever.
That way, the endpoints are more tightly defined and the
daemon-didnt-send-quit problem gets solved. In fact, the quit message
might become unneeded: just use close()?
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
