@@ -608,7 +608,6 @@ Network Support
608608  - "cm" supports a smaller number of networks (and they cannot be
609609    used together), but may provide better overall MPI performance:
610610
611-     - Myrinet MX and Open-MX
612611    - QLogic InfiniPath / Intel True Scale PSM
613612    - Intel Omni-Path PSM2
614613    - Mellanox MXM
@@ -685,9 +684,8 @@ Network Support
685684  v2.6.15 with libibverbs v1.1 or later (first released as part of
686685  OFED v1.2), per restrictions imposed by the OFED network stack.
687686
688- - The Myrinet MX BTL has been removed; MX support is now only
689-   available through the MX MTL.  Please use a prior version of Open
690-   MPI is you need the MX BTL support.
687+ - Support for Myrinet MX has been removed. Please use a prior version of Open
688+   MPI if you need the MX support.
691689
692690- Linux "knem" support is used when the "vader" or "sm" (shared
693691  memory) BTLs are compiled with knem support (see the --with-knem
@@ -873,21 +871,6 @@ NETWORKING SUPPORT / OPTIONS
873871  directory>/lib64, which covers most cases.  This option is only
874872  needed for special configurations.
875873
876- --with-mx=<directory>
877-   Specify the directory where the MX libraries and header files are
878-   located.  This option is generally only necessary if the MX headers
879-   and libraries are not in default compiler/linker search paths.
880- 
881-   MX is the support library for Myrinet-based networks.  An open
882-   source software package named Open-MX provides the same
883-   functionality on Ethernet-based clusters (Open-MX can provide
884-   MPI performance improvements compared to TCP messaging).
885- 
886- --with-mx-libdir=<directory>
887-   Look in directory for the MX libraries.  By default, Open MPI will
888-   look in <mx directory>/lib and <mx directory>/lib64, which covers
889-   most cases.  This option is only needed for special configurations.
890- 
891874--with-mxm=<directory>
892875  Specify the directory where the Mellanox MXM library and header
893876  files are located.  This option is generally only necessary if the
@@ -1942,8 +1925,7 @@ Each framework typically has one or more components that are used at
19421925run-time.  For example, the btl framework is used by the MPI layer to
19431926send bytes across different types underlying networks.  The tcp btl,
19441927for example, sends messages across TCP-based networks; the openib btl
1945- sends messages across OpenFabrics-based networks; the MX btl sends
1946- messages across Myrinet MX / Open-MX networks.
1928+ sends messages across OpenFabrics-based networks.
19471929
19481930Each component typically has some tunable parameters that can be
19491931changed at run-time.  Use the ompi_info command to check a component
@@ -2034,11 +2016,9 @@ passed on the mpirun command line will override an environment
20342016variable; an environment variable will override the system-wide
20352017defaults.
20362018
2037- Each component typically activates itself when relavant.  For example,
2038- the MX component will detect that MX devices are present and will
2039- automatically be used for MPI communications.  The SLURM component
2040- will automatically detect when running inside a SLURM job and activate
2041- itself.  And so on.
2019+ Each component typically activates itself when relavant.  For
2020+ example, the SLURM component will automatically detect when running
2021+ inside a SLURM job and activate itself.  And so on.
20422022
20432023Components can be manually activated or deactivated if necessary, of
20442024course.  The most common components that are manually activated,
0 commit comments