On Thu, 2017-07-27 at 16:18 -0600, Jason Gunthorpe wrote:
> On Tue, Jul 25, 2017 at 11:39:47AM -0600, Jason Gunthorpe wrote:
> > > > +# Hardware that supports RoCE
> > > > +DRIVERS=="be2net", ENV{ID_RDMA_ROCE}="1"
> > > > +DRIVERS=="bnxt_en", ENV{ID_RDMA_ROCE}="1"
> > > > +DRIVERS=="hns", ENV{ID_RDMA_ROCE}="1"
> > > > +DRIVERS=="i40e", ENV{ID_RDMA_ROCE}="1"
> > > > +DRIVERS=="mlx4_core", ENV{ID_RDMA_ROCE}="1"
> > > > +DRIVERS=="mlx5_core", ENV{ID_RDMA_ROCE}="1"
> > > > +DRIVERS=="qede", ENV{ID_RDMA_ROCE}="1"
> > >
> > > Should the "rdma_rxe" driver be added to this list?
> >
> > No.. I need to figure out something else for rxe. We have no way in
> > RDMA to determine the driver binding to the RDMA device (eg like
>
> This looks like a good bet for now:
>
> DEVPATH=="*/infiniband/rxe*", ATTR{parent}=="*", ENV{ID_RDMA_ROCE}="1"
>
> Now that I'm looking at rxe I notice that srp_daemon starts
> automatically for roce ports.
>
> I assume this is not desired?
Hello Jason,
The srp_daemon communicates with the IB SA to discover SRP target ports. As
you know there is no SA in a RoCE network. I think it is harmless to start
srp_daemon against a RoCE port but I don't think this makes sense.
Bart.--
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
