On Thu, Oct 30, 2014 at 07:54:30PM -0400, [email protected] wrote: > From: Ira Weiny <[email protected]> > > rdma-ndd is a system daemon which watches the procfs hostname file for > updates. > > Upon detecting an update it will update the Node Descriptions of the RDMA > devices in the system. > > This deamon is intended to work with kernels which support polling of the > procfs hostname file. If your kernel does not support this feature the daemon > will set the Node Descriptions to the hostname at start up and then sleep > forever.
It seems so strange to have kernel processing of %h/etc and then to turn around and use a user space daemon to connect one bit of the kernel to another.... Sadly, I think the proper way to address this is the same way netdev addresses it - do not activate the interface on module load, wait for an explicit enablement so userspace can configure before it tries to link up. (Not to say that is even possible considering RDMA's history, but still..) TBH, I'd rather see just this daemon and drop the kernel side... If the daemon is started before the modules are loaded then it might be able to set the description while the port is still down. Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
