Changeset 5714

Show
Ignore:
Timestamp:
11/05/09 15:05:49 (3 weeks ago)
Author:
balaji
Message:

Add information about some of the environment variables in
README.vin. Fixes ticket #924.

Reviewed by buntinas.

Files:
1 modified

Legend:

Unmodified
Added
Removed

  • mpich2/trunk/README.vin

    r5680 r5714  
    3535VII.  Shared Libraries 
    3636VIII. Other Features 
    37 IX.   Developer Builds 
    38 X.    Building ROMIO into MPICH2 
    39 XI.   Testing the MPICH2 installation 
    40 XII.  Installing MPICH2 on windows 
     37IX.   Environment Variables 
     38X.    Developer Builds 
     39XI.   Building ROMIO into MPICH2 
     40XII.  Testing the MPICH2 installation 
     41XIII. Installing MPICH2 on windows 
    4142 
    4243 
    … …  
    918919------------------------------------------------------------------------- 
    919920 
    920 IX. Developer Builds 
    921 ==================== 
     921IX. Environment Variables 
     922========================= 
     923 
     924MPICH2 provides several environment variables that have different 
     925purposes. 
     926 
     927Generic Environment Variables 
     928----------------------------- 
     929 
     930  MPICH_NO_LOCAL - Disable shared-memory communication. With this 
     931         option, even communication within a node will use the network 
     932         stack. 
     933 
     934               ************************************ 
     935 
     936  MPICH_INTERFACE_HOSTNAME - Network interface to use for 
     937         communication. By default MPICH2 picks the network interface 
     938         representing the hostname (gotten by gethostbyname). Consider 
     939         the following example: 
     940 
     941% /sbin/ifconfig 
     942 
     943eth0      Link encap:Ethernet  HWaddr 00:14:5E:57:C4:FA 
     944          inet addr:192.148.3.182  Bcast:192.148.248.255  Mask:255.255.255.0 
     945          inet6 addr: fe80::214:5eff:fe57:c4fa/64 Scope:Link 
     946          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1 
     947          RX packets:989925894 errors:0 dropped:7186 overruns:0 frame:0 
     948          TX packets:1480277023 errors:0 dropped:0 overruns:0 carrier:0 
     949          collisions:0 txqueuelen:1000 
     950          RX bytes:441568994866 (411.2 GiB)  TX bytes:1864173370054 (1.6 TiB) 
     951          Interrupt:185 Memory:e2000000-e2012100 
     952 
     953myri0     Link encap:Ethernet  HWaddr 00:14:5E:57:C4:F8 
     954          inet addr:10.21.3.182  Bcast:10.21.255.255  Mask:255.255.0.0 
     955          inet6 addr: fe80::214:5eff:fe57:c4f8/64 Scope:Link 
     956          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1 
     957          RX packets:3068986439 errors:0 dropped:7841 overruns:0 frame:0 
     958          TX packets:2288060450 errors:0 dropped:0 overruns:0 carrier:0 
     959          collisions:0 txqueuelen:1000 
     960          RX bytes:3598751494497 (3.2 TiB)  TX bytes:1744058613150 (1.5 TiB) 
     961          Interrupt:185 Memory:e4000000-e4012100 
     962 
     963In the above case the 192.148.x.x IP series refers to the standard 
     964Ethernet (or Gigabit Ethernet) network, AND the 10.21.x.x series 
     965refers to Myrinet. 
     966 
     967To run over the Myrinet network use: 
     968 
     969% mpiexec -np 1 -env MPICH_INTERFACE_HOSTNAME 10.21.3.182 ./foo 
     970 
     971               ************************************ 
     972 
     973  MPICH_INTERFACE_HOSTNAME_R%d - Network interface to use for rank %d. 
     974 
     975               ************************************ 
     976 
     977  MPICH_PORT_RANGE - Port range to use for MPICH2 internal TCP 
     978         connections. This is useful when some of the host ports are 
     979         blocked by a firewall. For example, setting MPICH_PORT_RANGE 
     980         to "2000:3000" will ensure that MPICH2 will internally only 
     981         uses ports between 2000 and 3000. 
     982 
     983------------------------------------------------------------------------- 
     984 
     985X. Developer Builds 
     986=================== 
    922987For MPICH2 developers who want to directly work on the svn, there are 
    923988a few additional steps involved (people using the release tarballs do 
    … …  
    928993------------------------------------------------------------------------- 
    929994 
    930 X. Building ROMIO into MPICH2 
    931 ============================= 
     995XI. Building ROMIO into MPICH2 
     996============================== 
    932997By default, ROMIO, an implementation of the I/O portion of MPI-2 will 
    933998be built as a part of MPICH2. The file systems to be built can be 
    … …  
    9451010------------------------------------------------------------------------- 
    9461011 
    947 XI. Testing the MPICH2 installation 
    948 =================================== 
     1012XII. Testing the MPICH2 installation 
     1013==================================== 
    9491014To test MPICH2, use the following options after installing mpich2. 
    9501015These will assume that mpich2 is installed into /usr/local/mpich2. 
    … …  
    9581023------------------------------------------------------------------------- 
    9591024 
    960 XII. Installing MPICH2 on Windows 
    961 ================================= 
     1025XIII. Installing MPICH2 on Windows 
     1026================================== 
    9621027 
    9631028Here are the instructions for setting up MPICH2 on a Windows machine: