PM Installation Manual

[English], [Japanese]
  • Operating environment
  • Installing the Myrinet device driver
  • Making the Myrinet device
  • Setting up the PM configuration file
  • Testing PM
  • Trouble shooting

  • Installing the Myrinet device driver

    SunOS4
    After compiling and installing the device driver described in "Creating executable images", append the following line at the end of /etc/rc.local, then reboot the system.
    modload $(INSTALL_ROOT)/driver/myrinet.o -entry _myri_vdcmd -exec $(INSTALL_ROOT)/driver/myri_mkdev.sh
    
    When a Myrinet card is installed, the following kernel messages will be shown in the booting sequence:
    myri0: Updating L4.1 clockval to 50e450e4
    myri0: clockval = 50e450e4, cpu = 401, board = 0, sram_size = 40000
    myri0: 5 contexts using 640K bytes of memory
    myri0: sram = ff0be000, reg = ff0bd000, ctrl = ff0bc000, intr = 4, ipl = 700
    MYRICOM,mlanai0 at  SBus slot 2 0x80000 pri 7 (sbus level 4)
    
    These values depend on the version of the Myrinet card and the host system.

    NetBSD-1.2.1/i386
    Compile and install the device driver according the procedure described in "Creating executable images", then reboot the system.
    When a Myrinet card is installed, the following kernel messages will be shown in booting sequence:
    myri0 at pci0 dev 19 function 0
    myri0: clockval = 50e450e4, cpu = 401, delay = 1e, board = 1, sram = 100000
    myri0: 28 contexts using 3584K bytes of memory
    myri0: interrupting at irq 10
    
    These values depend on the version of the Myrinet card and the host system.

    Linux-2.0.33/i386
    Compile and install the device driver according the procedure described in "Creating executable images", then reboot the system.
    When a Myrinet card is installed, the following kernel messages will be shown in booting sequence:
    Myrinet 11 iobase(fe000000) irq(a) vmem(d0804000)
    myri_pm_init: register myri as major(120)
    myri_pm_attach
    myri: clockval = 50e450e4, cpu = 401, delay = 1e, board = ffff, sram = 40000
    
    These values depend on the version of the Myrinet card and the host system.

    Making the Myrinet device

    SunOS4
    /dev/myri0 is automatically created by myri_mkdev.sh which is invoked when modload is executed.

    NetBSD-1.2.1/i386
    Create /dev/myri0 as follows.
    # mknod /dev/myri0 c 44 0
    # chmod 666 /dev/myri0
    
    Linux-2.0.33/i386
    Create /dev/myri0 as follows.
    # mknod /dev/myri0 c 120 0
    # chmod 666 /dev/myri0
    

    Setting up the PM configuration file

    File name
    $(INSTALL_ROOT)/lib/score.conf

    Syntax of the configuration file
    The PM configuration file consists of three kinds of lines.
    A single '#' character indicates that the rest of the line is a comment, and to be ignored.

    An example of a PM configuration file
    This is an example of the configuration file.
    In this example, four nodes: node0, node1, node2 and node3 are connected by two Myrinet switches. Routes between node0, node1 and node2, node3 are distributed to two inter-switch links by routing specification lines.
    #
    # Sample configuration file
    #
    
    #
    # Node specification
    #  NodeNumber   Hostname        switchNumber.portNumber
    0               node0           0.0
    1               node1           0.1
    2               node2           1.0
    3               node3           1.1
    
    #
    # Switch specification
    #  switch       switchNumber.portNumber switchNumber.portNumber
    switch          0.2                     1.2
    switch          0.3                     1.3
    
    #
    # Routing specification
    # search        switchNumber    portNumber ...
    search          0               0 2 1 3
    search          1               0 2 1 3
    

    Testing PM

    Loop-back test
    The loop-back test sends messages to itself, the messages are returned by a Myrinet switch to the sender node. The Myrinet card must be connected to a switch.
    node0% pmload -mcp mcp_file -conf config_file
    node0% pmtest -dest 0 -ping
    8 9.10638e-06
    
    Ping-pong test
    The ping-pong test transfers messages between two nodes.
    node1% pmload -mcp mcp_file -conf config_file
    node1% pmtest -reply
    
    node0% pmload -mcp mcp_file -conf config_file
    node0% pmtest -dest 1 -ping
    8 1.50343e-05
    

    Trouble shooting

    Pmload causes a error.
    Loop back test fails.
    Ping-pong test fails.

    $Id: install.html,v 1.9 1998/06/02 11:50:31 kameyama Exp $