On Mon, Nov 10, 2014 at 06:32:18PM +0000, Weiny, Ira wrote: > > I don't know if this is practical, but it is the only race free way to > > properly > > address all of this. > > I don't think it is practical at all. > > Assuming that we can hold the link from transitioning to Init how
PortInfo writes can do that > does any userspace software know if the current hostname is "valid"? > If, at the time of module load, the hostname is "localhost" you end > up with the same "problem" as the proposed kernel patches. Deciding when to turn on the IB interface in the boot sequence is a policy issue for userspace. Some setups will require this to be done in the initrd (ie boot over IB), others will want to do this after management networking comes up (and the host name is set). Once rdma-ndd starts running the hostname will track just the same as if there was kernel %h support, and having your init sequence the IB interface up after you have the hostname ensures it isn't local host. This sequencing creates the opportunity for the admin to actually set the host name to something that is not the kernel default. > I'm not against adding this to rdma-ndd but I would like it to be > optional. With the kernel patches rdma-ndd itself is optional. Not really, without rdma-ndd the node description is able to change on its own and no traps are generated. That seems pretty broken. So you need to run rdma-ndd to have IBA compliance. > I think changing the default is a worthwhile change. In addition, > alternate admin policies are aided by the general use of the %h > specifier. I think you need to resolve this split responsibility somehow. The kernel needs to work correctly without the daemon. To me that either means it never changes the node desc on its own (what we have today), or it always generates a trap when it changes. > Do you believe that "<hostname> <device>" is an unreasonable default? No, but what if I want it to say "OSD <hostname> <device>" on some systems - then what? How do I set that and avoid generating traps at boot? 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
