On Thu, 2017-07-13 at 16:41 -0600, Jason Gunthorpe wrote: > On Thu, Jul 13, 2017 at 10:36:49PM +0000, Bart Van Assche wrote: > > On Thu, 2017-07-13 at 16:15 -0600, Jason Gunthorpe wrote: > > > The one nit that I don't have an easy solution for is starting modules > > > depending on the device technology, eg not starting srp or ipoib on > > > !IB devices. The issue is that I can't think of an easy way to detect > > > the device technology from the udev rule, at least not without a > > > helper script or additional kernel sysfs.. > > > > Are users expected to modify the kernel-boot/modules/*.conf files? I > > expect that only a minority of the RDMA users will want to load the ib_srpt > > and ib_isert kernel modules. > > I'd say in the same way they would be expected to modify the RedHat > /etc/rdma/rdma.conf file. I copied the defaults from that file, which > was to autoload target drivers. > > I agree with you, they probably don't make sense to be defaulted on. > Ideally their respective supporting packages or kernel would ensure > the modules autoload if someone is working with RDMA... I know nothing > about the target infrastructure - can you see a way to do that? Hello Jason, Users who want to enable RDMA target functionality probably will know the names of the kernel modules that provide such functionality. On Debian systems the names of these kernel modules can e.g. be added to /etc/modules. However, I'm not sure all distro's have an equivalent of the /etc/modules file. 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
