> >
> > Hey Jason,
> >
> > Thanks for doing all this! I'm testing with cxgb4 today.
> >
> > I get these errors building the rpms using the spec file in your tree:
>
> I think you are using ./rdma-core.spec? I forgot about that one and
> didn't make it work, I will fix it.
>
> You probably want to use redhat/rdma-core.spec anyhow?
>
Ok. I haven't been paying attention to the distro-specific stuff. I had a
process I have been following to build an rpm from ./rdma-core.spec. I'll try
the redhat spec file since I'm installing on a RHEL7.2 system.
> When testing, you want to start with a system that doesn't load any
> modules, then install the new rpms and see what happens. (rdma-core, iwpmd)
>
I've uninstalled all the pertinent packages, I think, with this:
yum autoremove -y libibverbs librdmacm libibumad libiwpm
> For iwarp I expect that systemd will auto start these units:
>
> rdma-load-modules@iwpmd.service loaded active exited Load RDMA
> modules from /etc/rdma/modules/iwpmd.conf
> rdma-load-modules@rdma.service loaded active exited Load RDMA
modules
> from /etc/rdma/modules/rdma.conf
> rdma-load-modules@iwarp.service loaded active exited Load RDMA
modules
> from /etc/rdma/modules/iwarp.conf
> iwpmd.service loaded active running iWarp Port
Mapper
>
> And you should have a reasonable set of modules loaded. Check the
> journal for interesting errors also..
>
Will do.
> For cxgb4 these are the two critical udev lines:
>
> ENV{ID_NET_DRIVER}=="cxgb4", RUN{builtin}+="kmod load iw_cxgb4"
> DRIVERS=="cxgb4", ENV{ID_RDMA_IWARP}="1"
>
> The first should load iw_cxgb4 if an ethernet device with the cxgb4
> driver is found (the driver name being matched is as reported by
> ethtool -i)
>
> Both need to trigger for things to work properly, you can check with:
>
> $ udevadm info /sys/class/net/ethX
> $ udevadm info /sys/class/infiniband/cxgb4_0 # ??
>
Thanks! I'll let you know how it goes.
Steve.
--
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
