PM-II ETHERNET CONF(5) | PM-II ETHERNET CONF(5) |
NodeNumber MAC address Hostname
NodeNumber
MAC address
Hostname
hostname
command returns. PM/Ethernet itself
doesn't depend on this constraint, thus, the pmtest
command doesn't detect a problem about this, but upper-level
software depends on this.
0 00:00:12:23:34:45 xxx.yyy.xxx |
unit unit_numberSpecify unit number of this configuration.
unit 0 |
checksum 0(off) or 1(on)Enable data checksum. If you application fails or results of caliculateion is wrong. Set this value 1, and re-run your application. If data checksum error occur, the error is showed by /proc/pm/ethernet/[ethernet-unit-num]/info. In some sitiation, we found a checksum error on NIC DMA(sending or receiving).
comp0.pccluster.org.% cat /proc/pm/ethernet/3/info PM Ethernet 0310 Version : "$Id: pm-ether-conf.html,v 1.9 2000/09/13 18:12:12 soda Exp $" device : eth3 irq : 5 MTU : 1468 Bytes maxnodes : 128 Intreap : on Checksum : on dev error : 8504 header err : 0 header cksum err: 50 data cksum err : 5 underrun err : 0 |
checksum 1 |
maxnsend
optionmaxnsend 8 - 32Define number of sending packets at a time. When you use network trunking, you should increase this parameter from default value.
maxnsend 16 |
backoff
optionbackoff 1000 - 20000(usec)Define a re-transmitting time. This value is very important on large node cluster or an application which uses all to all communication.
backoff 4800 |
# # Sample configuration file # unit 0 checksum 1 # # Node specification # NodeNumber MAC address Hostname 0 00:00:f3:51:03:00 comp0.pccluster.org 1 00:00:f3:51:03:01 comp1.pccluster.org 2 00:00:f3:51:03:02 comp2.pccluster.org 3 00:00:f3:51:03:03 comp3.pccluster.org |
![]() |
PC Cluster Consortium |