Myrinet GM-1 Software
for Mac OS X

To download Myrinet software, you need a login and password.
If you don't already have these, please request them.

Binary | Source

Note: Recent Apple Power Mac G4s have 64-bit, 33MHz PCI slots with sufficient performance between the PCI bus and system memory to benefit from Myrinet. This software will work on earlier PowerMac models under Mac OS X 10.1 and 10.2, but the performance will be limited by the PCI bus.

The Mac OS X GM software is distributed in both source and binary forms, and supports Mac OS X version 10.1.x and 10.2.x on the Power PC platform.

Recommended-version GM Binary Downloads for Mac OS X
NIC
Operating System / Architecture PCI64B and PCI64C
(Lanai 9)		 PCI64 and PCI64A
(Lanai 7)
Mac OS X 10.1.x for Power PC GM-1.6.3 for MacOSX 10.1 GM-1.6.3 for MacOSX 10.1
Mac OS X 10.2.x for Power PC GM-1.6.3 for MacOSX 10.2 GM-1.6.3 for MacOSX 10.2

VERY IMPORTANT NOTE: The installation procedure for GM has changed significantly between gm-1.5.2.4 and gm-1.6.3. Refer to the abbreviated installation instructions below. Automated installation scripts will need to be updated!

Abbreviated Binary Installation Instructions

Please be sure to read the README files (README and README-MacOSX) for detailed installation instructions and architecture-specific troubleshooting. Unresolved questions could also be answered in the FAQ.

Current cautions and common problems:

  • GM-1 does not support the new M3-CLOS and M3-SPINE Myrinet-2000 switches.
  • If you are using an Apple G4 Xserve mother board, please read this FAQ entry for important performance information.
  • Incorrectly written programs which attempt to free() or munmap() memory prior to deregistering it may "hang" indefinitely. For details see README-MacOSX.
  • The ethernet emulation device is named "enX" rather than "myriX" For details see README-MacOSX.
  • If you have a mixture of hosts with Lanai4 and Lanai7 (or Lanai9) NICs that need to talk to each other, you must build from source and configure with --disable-new-features on all of the hosts.
  • By default, GM-1.5 and higher has security features enabled. Thus, you must now be root to run the GM Mapper (or gm_simpleroute).
  • If the host is rebooted, you must rerun the GM Mapper.
  • The GM Mapper must be run before any communication over Myrinet can occur.
  • In most cases, the GM Mapper should not be run continuously. It is intrusive and can interfere with network traffic intensive jobs (e.g, MPI applications).

    • GM installation is performed in four easy steps:

    1. Unpacking the GM driver.

    When reading the instructions below, please replace VERSION with your operating system version (10.1, 10.2).

            tar zxvf gm-1.6.3_MacOSX-VERSION-new-features-8ports.tar.gz
        cd gm-1.6.3_MacOSX-VERSION-new-features-8ports

    2. Installing the GM driver.

    Select an installation directory path <install_path>. It is usually best for <install_path> to be the path to an NFS directory available on all machines that are to share this GM installation. The directory must be accessible using <install_path> on all machines that are to share the installation. <install_path> must be an absolute path; it must start with /. However, <install_path> may contain symbolic links. 

            cd binary
        ./GM_INSTALL <install_dir>

    You may omit <install_dir> to install the driver in /opt/gm/.

    Next, you must run 

            sudo <install_path>/sbin/gm_install_drivers

    on each machine to install the drivers on that machine.

    If you wish for the driver to auto-load an boot, you must copy StartupParameters.plist to the /System/Library/StartupItems/GM/ directory: 

            sudo cp <install_path>/etc/StartupParameters.plist /System/Library/StartupItems/GM/

    Alternatively, you may start and stop the drivers manually using 

            sudo /System/Library/StartupItems/GM/gm start
        sudo /System/Library/StartupItems/GM/gm stop

    or 

            sudo /System/Library/StartupItems/GM/gm restart

    to start, stop, or restart the driver, respectively.

    For directions on how to uninstall the GM driver, refer to the "Miscellaneous" section of the README-MacOSX.

    Note: If the host is rebooted, you must reload the GM driver (and rerun the GM mapper).

    3. Running the GM Mapper.

            cd <install_path>/binary/sbin/
        sudo ./mapper ../etc/gm/map_once.args

    There are 3 ways in which the GM Mapper can be run. Refer to section 2 'Running the Mapper' of the README-linux for details.

    4. Testing the GM Installation.

    A variety of test scripts are available in binary/bin/ to test your GM installation. We recommend the five tests described in tests/README.

    Congratulations! You have successfully installed GM.

    Recommended-version GM Source Downloads for Mac OS X
    NIC
    Operating System / Architecture PCI64B and PCI64C
    (Lanai 9)    		 PCI64 and PCI64A
    (Lanai 7)
    Mac OS X 10.1.x and 10.2.x for Power PC GM-1.6.3_MacOSX GM-1.6.3_MacOSX

    VERY IMPORTANT NOTE: The installation procedure for GM has changed significantly between gm-1.5.2.4 and gm-1.6.3. Refer to the abbreviated installation instructions below. Automated installation scripts will need to be updated!

    Abbreviated Source Installation Instructions

    To compile GM on Mac OS X platforms, you will need GNU make, and the Apple C/C++ compiler. These tools are provided by Apple as part of the Developer Tools package available through the Apple Developer Connection. The Developer Tools package is also included in the Mac OS X 10.2 retail box. Please be sure to read the README files (README and README-MacOSX) for detailed installation instructions and architecture-specific troubleshooting. Unresolved questions could also be answered in the FAQ.

    Current cautions and common problems:

  • GM-1 does not support the new M3-CLOS and M3-SPINE Myrinet-2000 switches.
  • If you are using an Apple G4 Xserve mother board, please read this FAQ entry for important performance information.
  • You may not use the --enable-maintainer-mode flag on Mac OS X. For details see README-MacOSX.
  • Incorrectly written programs which attempt to free() or munmap() memory prior to deregistering it may "hang" indefinitely. For details see README-MacOSX.
  • The ethernet emulation device is named "enX" rather than "myriX" For details see README-MacOSX.
  • By default, GM-1.5 and higher assumes that you have Lanai9 or Lanai7 NICs. If you have Lanai4 NICs with 1MB or 512KB memory, you must configure with --disable-new-features.
  • If you have a mixture of hosts with Lanai4 and Lanai7 (or Lanai9) NICs that need to talk to each other, you must configure with --disable-new-features on all of the hosts.
  • By default, GM-1.5 and higher has security features enabled. Thus, you must now be root to run the GM Mapper (or gm_simpleroute).
  • Do not use the configure flag --enable-directcopy with GM 1.6.3 This flag is not a valid option to GM 1.6.3. It will be re-enabled in a future release.
  • If the host is rebooted, you must rerun the GM Mapper.
  • The GM Mapper must be run before any communication over Myrinet can occur.
  • In most cases, the GM Mapper should not be run continuously. It is intrusive and can interfere with network traffic intensive jobs (e.g, MPI applications).

    • GM installation is performed in four easy steps:

    1. Configuring and compiling the GM driver

            tar zxvf gm-1.6.3_MacOSX.tar.gz
        cd gm-1.6.3_MacOSX
        ./configure
        make

    2. Installing the GM driver.

    Select an installation directory path <install_path>. It is usually best for <install_path> to be the path to an NFS directory available on all machines that are to share this GM installation. The directory must be accessible using <install_path> on all machines that are to share the installation. <install_path> must be an absolute path; it must start with /. However, <install_path> may contain symbolic links. 

            cd binary
        ./GM_INSTALL <install_dir>

    You may omit <install_dir> to install the driver in /opt/gm/.

    Next, you must run 

            sudo <install_path>/sbin/gm_install_drivers

    on each machine to install the drivers on that machine.

    If you wish for the driver to auto-load an boot, you must copy StartupParameters.plist to the /System/Library/StartupItems/GM/ directory: 

            sudo cp <install_path>/etc/StartupParameters.plist /System/Library/StartupItems/GM/

    Alternatively, you may start and stop the drivers manually using 

            sudo /System/Library/StartupItems/GM/gm start
        sudo /System/Library/StartupItems/GM/gm stop

    or 

            sudo /System/Library/StartupItems/GM/gm restart

    to start, stop, or restart the driver, respectively.

    For directions on how to uninstall the GM driver, refer to the "Miscellaneous" section of the README-MacOSX.

    Note: If the host is rebooted, you must reload the GM driver (and rerun the GM mapper).

    3. Running the GM Mapper.

            cd <install_path>/binary/sbin/
        sudo ./mapper ../etc/gm/map_once.args

    There are 3 ways in which the GM Mapper can be run. Refer to section 2 'Running the Mapper' of the README-linux for details.

    4. Testing the GM Installation.

    A variety of test scripts are available in binary/bin/ to test your GM installation. We recommend the five tests described in tests/README.

    Congratulations! You have successfully installed GM.

    Refer to the Software and Documentation Page for details of GM-based software (MPICH-GM, PVM on GM). If you encountered difficulties during any phase of this installation process, we recommend that you first consult the README-MacOSX and FAQ, and if you still have unresolved questions, please feel free to contact technical support at help@myri.com.


    Last updated: 19 May 2006