1
1

Clarify the comment: we ''do'' apply the memory policy before main()

starts... unless you direct launch MPI applications, in which case the
policy isn't in effect until MPI_INIT completes.

This commit was SVN r26823.
Этот коммит содержится в:
Jeff Squyres 2012-07-20 22:46:34 +00:00
родитель 12d99a9ebb
Коммит 11feeb61f3

Просмотреть файл

@ -96,7 +96,7 @@ int opal_hwloc_base_open(void)
break;
}
mca_base_param_reg_string_name("hwloc", "base_mem_alloc_policy",
"Policy to determine where general memory allocations are placed after MPI_INIT (this is not memory binding). A value of \"none\" means that no memory policy is applied. A value of \"local_only\" means that all memory allocations will be restricted to the local NUMA node where each process is placed. Note that operating system paging policies are unaffected by this setting. For example, if \"local_only\" is used and local NUMA node memory is exhausted, a new memory allocation may cause paging.",
"Policy to determine where general memory allocations are placed (this is not memory binding). If using direct launch, this policy will not be in effect until after MPI_INIT. A value of \"none\" means that no memory policy is applied. A value of \"local_only\" means that all memory allocations will be restricted to the local NUMA node where each process is placed. Note that operating system paging policies are unaffected by this setting. For example, if \"local_only\" is used and local NUMA node memory is exhausted, a new memory allocation may cause paging.",
false, false, str_value, &str_value);
if (strcasecmp(str_value, "none") == 0) {
opal_hwloc_base_map = OPAL_HWLOC_BASE_MAP_NONE;