[Labeled-nfs] Pipes vs Netlink

[Trond Myklebust]

On Wed, 2007-09-12 at 09:52 -0400, David P. Quigley wrote:
> situations.
> 
> The second option is to use netlink sockets. In this method we remove
> the need for rpc_pipefs. The user space daemon would listen on a
> particular netlink socket and have the kernel open up a connection to
> this socket for each client it starts. In this method the client is
> needs to maintain a mapping from a unique client id to the internal data
> for that client. The benefits to this is that the user space daemon
> implementation will be simpler since we don't need to bother with the
> dnotify code that idmapd currently uses. One of the downsides is that
> netlink is a connectionless method so we would need to build basic
> retransmission into both the kernel and user space code if we want to be
> reliable. 

netlink blows goats. It has all the overhead of the full networking
stack for absolutely no gain whatsoever in either simplicity or
reliability.

Trond