474564a6b1
addition to my design and testing, it was conceptually approved by
Gil, Gleb, Pasha, Brad, and Galen. Functionally [probably somewhat
lightly] tested by Galen. We may still have to shake out some bugs
during the next few months, but it seems to be working for all the
cases that I can throw at it.
Here's a summary of the changes from that branch:
* Move MCA parameter registration to a new file (btl_openib_mca.c):
* Properly check the retun status of registering MCA params
* Check for valid values of MCA parameters
* Make help strings better
* Otherwise, the only default value of an MCA param that was
changed was max_btls; it went from 4 to -1 (meaning: use all
available)
* Properly prototyped internal functions in _component.c
* Made a bunch of functions static that didn't need to be public
* Renamed to remove "mca_" prefix from static functions
* Call new MCA param registration function
* Call new INI file read/lookup/finalize functions
* Updated a bunch of macros to be "BTL_" instead of "ORTE_"
* Be a little more consistent with return values
* Handle -1 for the max_btls MCA param
* Fixed a free() that should have been an OBJ_RELEASE()
* Some re-indenting
* Added INI-file parsing
* New flex file: btl_openib_ini.l
* New default HCA params .ini file (probably to be expanded over
time by other HCA vendors)
* Added more show_help messages for parsing problems
* Read in INI files and cache the values for later lookup
* When component opens an HCA, lookup to see if any corresponding
values were found in the INI files (ID'ed by the HCA vendor_id
and vendor_part_id)
* Added btl_openib_verbose MCA param that shows what the INI-file
stuff does (e.g., shows which MTU your HCA ends up using)
* Added btl_openib_hca_param_files as a colon-delimited list of INI
files to check for values during startup (in order,
left-to-right, just like the MCA base directory param).
* MTU is currently the only value supported in this framework.
* It is not a fatal error if we don't find params for the HCA in
the INI file(s). Instead, just print a warning. New MCA param
btl_openib_warn_no_hca_params_found can be used to disable
printing the warning.
* Add MTU to peer negotiation when making a connection
* Exchange maximum MTU; select the lesser of the two
This commit was SVN r11182.
109 строки
3.6 KiB
Plaintext
109 строки
3.6 KiB
Plaintext
# -*- text -*-
|
|
#
|
|
# Copyright (c) 2004-2005 The Trustees of Indiana University and Indiana
|
|
# University Research and Technology
|
|
# Corporation. All rights reserved.
|
|
# Copyright (c) 2004-2005 The University of Tennessee and The University
|
|
# of Tennessee Research Foundation. All rights
|
|
# reserved.
|
|
# Copyright (c) 2004-2005 High Performance Computing Center Stuttgart,
|
|
# University of Stuttgart. All rights reserved.
|
|
# Copyright (c) 2004-2006 The Regents of the University of California.
|
|
# All rights reserved.
|
|
# $COPYRIGHT$
|
|
#
|
|
# Additional copyrights may follow
|
|
#
|
|
# $HEADER$
|
|
#
|
|
# This is the US/English general help file for Open MPI.
|
|
#
|
|
[ini file:file not found]
|
|
The Open MPI OpenIB BTL component was unable to find or read an INI
|
|
file that was requested via the btl_openib_hca_param_files MCA
|
|
parameter. Please check this file and/or modify the
|
|
btl_openib_hca_param_files MCA parameter:
|
|
|
|
%s
|
|
[ini file:not in a section]
|
|
In parsing Open IB BTL parameter file, values were found that were not
|
|
in a valid INI section. These values will be ignored. Please
|
|
re-check this file:
|
|
|
|
%s
|
|
|
|
At line %d, near the following text:
|
|
|
|
%s
|
|
[ini file:unexpected token]
|
|
In parsing Open IB BTL parameter file, unexpected tokens were found
|
|
(this may cause significant portions of the INI file to be ignored).
|
|
Please re-check this file:
|
|
|
|
%s
|
|
|
|
At line %d, near the following text:
|
|
|
|
%s
|
|
[ini file:expected equals]
|
|
In parsing Open IB BTL parameter file, unexpected tokens were found
|
|
(this may cause significant portions of the INI file to be ignored).
|
|
An equals sign ("=") was expected but was not found. Please re-check
|
|
this file:
|
|
|
|
%s
|
|
|
|
At line %d, near the following text:
|
|
|
|
%s
|
|
[ini file:expected newline]
|
|
In parsing Open IB BTL parameter file, unexpected tokens were found
|
|
(this may cause significant portions of the INI file to be ignored).
|
|
A newline was expected but was not found. Please re-check this file:
|
|
|
|
%s
|
|
|
|
At line %d, near the following text:
|
|
|
|
%s
|
|
[no hca params found]
|
|
WARNING: No HCA parameters were found for the HCA that Open MPI
|
|
detected:
|
|
|
|
Hostname: %s
|
|
HCA vendor ID: 0x%04x
|
|
HCA vendor part ID: %d
|
|
|
|
Default HCA parameters will be used, which may result in lower
|
|
performance. You can edit any of the files specified by the
|
|
btl_openib_hca_param_files MCA parameter to set values for your HCA.
|
|
|
|
NOTE: You can turn off this warning by setting the MCA parameter
|
|
btl_openib_warn_no_hca_params_found to 0.
|
|
[btl_openib:retry-exceeded]
|
|
The InfiniBand retry count between two MPI processes has been
|
|
exceeded. "Retry count" is defined in the InfiniBand spec 1.2
|
|
(section 12.7.38):
|
|
|
|
The total number of times that the sender wishes the receiver to
|
|
retry timeout, packet sequence, etc. errors before posting a
|
|
completion error.
|
|
|
|
This error typically means that there is something awry within the
|
|
InfiniBand fabric itself. You should note the hosts on which this
|
|
error has occurred; it has been observed that rebooting or removing a
|
|
particular host from the job can sometimes resolve this issue.
|
|
|
|
Two MCA parameters can be used to control Open MPI's behavior with
|
|
respect to the retry count:
|
|
|
|
* btl_openib_ib_retry_count - The number of times the sender will
|
|
attempt to retry (defaulted to 7, the maximum value).
|
|
|
|
* btl_openib_ib_timeout - The local ACK timeout parameter (defaulted
|
|
to 10). The actual timeout value used is calculated as:
|
|
|
|
4.096 microseconds * (2^btl_openib_ib_timeout)
|
|
|
|
See the InfiniBand spec 1.2 (section 12.7.34) for more details.
|