Re: [PATCH rdma-core 0/5] Common systemd/udev based boot support

[Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>]

On Tue, Jul 25, 2017 at 01:49:37PM -0500, Steve Wise wrote:

> After I rebooted, cxgb4 and iw_cxgb4 were loaded, but the services were not
> started.  I think that is probably due to the fact that iw_cxgb4 doesn't
> register with the rdma core until the cxgb4 interfaces are brought
> up.

Yes, it is done on demand when the kernel creates its side of the
interface.

> I then brought up port 0 of the cxgb4 card:
> 
> [root@stevo3 ~]# ip link set enp4s0f4 up
> [root@stevo3 ~]# ip addr add 172.16.3.3/24 dev enp4s0f4
> 
> And then the services were started:

Yep, everything you sent me looks fine, thanks for taking a look at
this.

This sort of hotplug that cxbg4 does is quite strange, what happens
when 'ip link set X down' is done? Does it remove the RDMA device?
Does 'ip link set down' block until all users go away?

This is going to make it harder for cxgb users to get a reliably
bootup at this time, we need more kernel autoloading for things to be
reliable, and I'm sure iwpmd.service needs some dependency adjusting,
I just don't know enough about it to do it right. :\

> I assume since iw_cxgb4 was loaded, that they worked.  Because before I
> installed rdma-core, after a reboot only cxgb4 was loaded.

Yep

Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html