On Mon, Oct 17, 2016 at 02:56:37PM -0400, Doug Ledford wrote: > Since it got snipped, I'm pretty sure it just lists opensm in the Wants= > tag. With systemd, that's a soft dependency. Only if opensm is > installed and configured to start anyway does systemd then order this > item after opensm. Since you need opensm for links to come up anyway, > it makes sense for the order of startup for RDMA related items to be: Daemons should not require opensm to be started to operate correctly. If they do we surely have a boot race bug that should be fixed, because we cannot rely on a remote SM to have configured the port the time window betweeen rdma.service completion and dependent service start. So I view every use of a opensm dependent in a unit file as either unnecessary or working around a bug.. Lets ID the bugs so we at least know where we stand.. Plus, there are more SM's than opensm, so we really should not hardwire a single SM in the service files upstream, but try and work with all the SMs... Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
