Hans Petter Selasky 1866c98e64 Infiniband clients must be attached and detached in a specific order in ibcore. ... Currently the linking order of the infiniband, IB, modules decide in which order the clients are attached and detached. For example one IB client may use resources from another IB client. This can lead to a potential deadlock at shutdown. For example if the ipoib is unregistered after the ib_multicast client is detached, then if ipoib is using multicast addresses a deadlock may happen, because ib_multicast will wait for all its resources to be freed before returning from the remove method. Fix this by using module_xxx_order() instead of module_xxx(). Differential Revision: https://reviews.freebsd.org/D23973 MFC after: 1 week Sponsored by: Mellanox Technologies		2020-07-06 08:50:11 +00:00
..
fw_qos.h
fw.h
icm.h
mlx4_alloc.c
mlx4_catas.c
mlx4_cmd.c	Improve support for switching to and from command polling mode in mlx4core.	2019-03-11 14:29:50 +00:00
mlx4_cq.c
mlx4_eq.c	mlx4en: Add support for netdump.	2018-12-05 13:32:15 +00:00
mlx4_fw_qos.c
mlx4_fw.c
mlx4_icm.c
mlx4_intf.c	mlx4: Make sure default VNET is set when adding a new interface.	2018-12-05 13:39:05 +00:00
mlx4_main.c	Infiniband clients must be attached and detached in a specific order in ibcore.	2020-07-06 08:50:11 +00:00
mlx4_mcg.c
mlx4_mr.c
mlx4_pd.c
mlx4_port.c
mlx4_profile.c
mlx4_qp.c
mlx4_reset.c
mlx4_resource_tracker.c
mlx4_sense.c
mlx4_srq.c
mlx4.h	Bump the Mellanox driver version numbers and the FreeBSD version number.	2019-05-08 11:15:07 +00:00