On Fri, Jul 14, 2017 at 06:23:13PM +0200, Benjamin Drung wrote:
> > My udev is not great, but something like this:
> >
> > DRIVER=="mlx4_core", ACTION=="add", TAG+="systemd", ENV{SYSTEMD_WANTS}="rdma-load-modules@mlx4"
> >
> > Might work better? I think that triggers on driver bind? Could you
> > try to switch your mlx and i40e drivers in that way?
>
> I tried it. It works as expected. rdma-load-modules@mlx4 is loaded and
> rdma-load-modules@i40e.service is not loaded. Not tested if the udev
> trigger will also work for used built-in modules.
Okay, I will change it to be like that and we can see what people
think.
> > The only solution to this kind of problem is to add more ordering,
> > Debian should include a patch to rdma-load-modules@ to put it before
> > their unique networking.service..
>
> Or patch rdma-load-modules@ to put it before network-pre.target
I think that would be OK.
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
