Fix a few code comments in the new ompi-top functionality.
This commit was SVN r20166.
Этот коммит содержится в:
родитель
7787f84540
Коммит
f911b1a63d
@ -46,7 +46,7 @@ static int query(pid_t pid, opal_pstats_t *stats);
|
||||
static int fini(void);
|
||||
|
||||
/*
|
||||
* Linux pstat module
|
||||
* Darwin pstat module
|
||||
*/
|
||||
const opal_pstat_base_module_t opal_pstat_darwin_module = {
|
||||
init,
|
||||
|
@ -14,21 +14,12 @@
|
||||
/**
|
||||
* @file
|
||||
*
|
||||
* pstat (memory checker) framework component interface.
|
||||
* pstat (process statistics) framework component interface.
|
||||
*
|
||||
* Intent
|
||||
*
|
||||
* This is a very thin framework to abstract memory checking tools,
|
||||
* such as valgrind and possibly Sun rtc (memory checking available
|
||||
* possibly only under Solaris/Sparc).
|
||||
* To support the ompi-top utility.
|
||||
*
|
||||
* Currently, only functionality for hiding and unhiding of memory
|
||||
* is added; further functions provided by the memory checker/api
|
||||
* checker could be added, however, this comes (at least for valgrind)
|
||||
* with considerable overhead.
|
||||
* One possible option would be to have error_print_callbacks, that
|
||||
* output different error messages, depending on the memory location
|
||||
* being hit by certain error.
|
||||
*/
|
||||
|
||||
#ifndef OPAL_MCA_PSTAT_H
|
||||
|
Загрузка…
Ссылка в новой задаче
Block a user