Re: [PATCH v2 rdma-core 1/6] Common infrastructure for auto loading rdma modules

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Jul 28, 2017 at 04:48:55PM -0500, Chien Tin Tung wrote:

> Sorry Jason, I can't test this till next week.  On inspection I found a couple of issues
> below.

Sure, thanks!

> > +# Hardware that supports InfiniBand
> > +DRIVERS=="mlx4_core", ENV{ID_RDMA_INFINIBAND}="1"
> > +DRIVERS=="mlx5_core", ENV{ID_RDMA_INFINIBAND}="1"
> > +DRIVERS=="qib", ENV{ID_RDMA_INFINIBAND}="1"
> > +
> > +# Hardware that supports OPA
> > +DRIVERS=="hfi1verbs", ENV{ID_RDMA_OPA}="1"
> > +
> > +# Hardware that supports iWarp
> > +DRIVERS=="cxgb3", ENV{ID_RDMA_IWARP}="1"
> > +DRIVERS=="cxgb4", ENV{ID_RDMA_IWARP}="1"
> 
> Need to add nes and i40e here under iWARP.

Okay, yes.. nes was missed because I was not able to guess the
ethernet driver name, I will add it and move i40e

> This is enough to autoload iwpmd for nes and i40e/i40iw, correct?

Yes, ID_RDMA_IWARP in the udev database does that and whatever else in
future we need.

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



[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]     [Yosemite Photos]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux