Performance tunning. The OB! progress functions just call the BML one. Thus, setting the
progress function in the mca_pml to the BML progress one, avoid having a cascade of call to the progress function and speed up a little bit the execution. This commit was SVN r9007.
Этот коммит содержится в:
родитель
08747dcaf8
Коммит
bbe79f7f0e
@ -214,8 +214,15 @@ mca_pml_base_module_t* mca_pml_ob1_component_init(int* priority,
|
||||
|
||||
|
||||
if(OMPI_SUCCESS != mca_bml_base_init( enable_progress_threads, enable_mpi_threads))
|
||||
return NULL;
|
||||
|
||||
return NULL;
|
||||
|
||||
/* As our own progress function does nothing except calling the BML
|
||||
* progress, let's modify the progress function pointer in our structure
|
||||
* to avoid useless functions calls. The event library will instead call
|
||||
* directly the BML function.
|
||||
*/
|
||||
mca_pml_ob1.super.pml_progress = mca_bml.bml_progress;
|
||||
|
||||
return &mca_pml_ob1.super;
|
||||
}
|
||||
|
||||
|
Загрузка…
x
Ссылка в новой задаче
Block a user