- fix typos
This commit was SVN r11703.
Этот коммит содержится в:
родитель
b49ff3a3b7
Коммит
80166a9516
@ -84,7 +84,7 @@
|
||||
* Progress:
|
||||
*
|
||||
* By default, the library provides for polling based progress of outstanding
|
||||
* requests. The BTL component exports an interface function (btlm_progress)
|
||||
* requests. The BTL component exports an interface function (btl_progress)
|
||||
* that is called in a polling mode by the PML during calls into the MPI
|
||||
* library. Note that the btlm_progress() function is called on the BTL component
|
||||
* rather than each BTL module. This implies that the BTL author is responsible
|
||||
@ -95,14 +95,14 @@
|
||||
* option of building with asynchronous threaded progress. In this case, the BTL
|
||||
* author is responsible for providing a thread to progress pending operations.
|
||||
* A thread is associated with the BTL component/module such that transport specific
|
||||
* functionality/APIs may be used to block the thread ubtll a pending operation
|
||||
* functionality/APIs may be used to block the thread until a pending operation
|
||||
* completes. This thread MUST NOT poll for completion as this would oversubscribe
|
||||
* the CPU.
|
||||
*
|
||||
* Note that in the threaded case the PML may choose to use a hybrid approach,
|
||||
* such that polling is implemented from the user thread for a fixed number of
|
||||
* cycles before relying on the background thread(s) to complete requests. If
|
||||
* possible the BTL should support the use of both modes concurrebtly.
|
||||
* possible the BTL should support the use of both modes concurrently.
|
||||
*
|
||||
*/
|
||||
|
||||
|
@ -140,7 +140,7 @@ int mca_btl_mvapi_component_open(void)
|
||||
mca_btl_mvapi_param_register_int ("max_btls", "maximum number of HCAs/ports to use",
|
||||
4, &tmp_int);
|
||||
mca_btl_mvapi_component.ib_max_btls = tmp_int;
|
||||
mca_btl_mvapi_param_register_int ("free_list_num", "intial size of free lists",
|
||||
mca_btl_mvapi_param_register_int ("free_list_num", "initial size of free lists",
|
||||
8, &mca_btl_mvapi_component.ib_free_list_num);
|
||||
mca_btl_mvapi_param_register_int ("free_list_max", "maximum size of free lists",
|
||||
-1, &mca_btl_mvapi_component.ib_free_list_max);
|
||||
|
@ -101,7 +101,7 @@ bool ompi_mpi_maffinity_setup = false;
|
||||
* corresponding dummy function that is invoked from this function).
|
||||
*
|
||||
* Additionally, there can be/are strange linking paths such that
|
||||
* ompi_info needs symbols symbols such as ompi_fortran_status_ignore,
|
||||
* ompi_info needs symbols such as ompi_fortran_status_ignore,
|
||||
* which, if they weren't here with a collection of other global
|
||||
* symbols that are initialized (which seems to force this .o file to
|
||||
* be pulled into the resolution process, because ompi_info certainly
|
||||
|
Загрузка…
x
Ссылка в новой задаче
Block a user