@@ -1020,15 +1020,33 @@ NETWORKING SUPPORT / OPTIONS
1020
1020
configurations.
1021
1021
1022
1022
--with-verbs-usnic
1023
+ Note that this option is no longer necessary in recent Linux distro
1024
+ versions. If your Linux distro uses the "rdma-core" package (instead
1025
+ of a standalone "libibverbs" package), not only do you not need this
1026
+ option, you shouldn't use it, either. More below.
1027
+
1023
1028
This option will activate support in Open MPI for disabling a
1024
1029
dire-sounding warning message from libibverbs that Cisco usNIC
1025
1030
devices are not supported (because Cisco usNIC devices are supported
1026
1031
through libfabric, not libibverbs). This libibverbs warning can
1027
1032
also be suppressed by installing the "no op" libusnic_verbs plugin
1028
1033
for libibverbs (see https://github.com/cisco/libusnic_verbs, or
1029
- download binaries from cisco.com). This option is disabled by
1030
- default because it causes libopen-pal.so to depend on libibverbs.so,
1031
- which is undesirable to many downstream packagers.
1034
+ download binaries from cisco.com).
1035
+
1036
+ This option is disabled by default for two reasons:
1037
+
1038
+ 1. It causes libopen-pal.so to depend on libibverbs.so, which is
1039
+ undesirable to many downstream packagers.
1040
+ 2. As mentioned above, recent versions of the libibverbs library
1041
+ (included in the "rdma-core" package) do not have the bug that
1042
+ will emit dire-sounding warnings about usnic devices. Indeed,
1043
+ the --with-verbs-usnic option will enable code in Open MPI that
1044
+ is actually incompatible with rdma-core (i.e., cause Open MPI to
1045
+ fail to compile).
1046
+
1047
+ If you enable --with-verbs-usnic and your system uses the rdma-core
1048
+ package, configure will safely abort with a helpful message telling
1049
+ you that you should not use --with-verbs-usnic.
1032
1050
1033
1051
--with-usnic
1034
1052
Abort configure if Cisco usNIC support cannot be built.
0 commit comments