From 96901d95032ced134460e14a027a1417892adcda Mon Sep 17 00:00:00 2001 From: Jeff Squyres Date: Tue, 29 May 2012 18:08:39 +0000 Subject: [PATCH] Slightly change the wording in the help message for the hwloc_base_mem_alloc_policy MCA parameter to be more explicit. This commit was SVN r26512. --- opal/mca/hwloc/base/hwloc_base_open.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/opal/mca/hwloc/base/hwloc_base_open.c b/opal/mca/hwloc/base/hwloc_base_open.c index 2ea090b2c5..98d926805c 100644 --- a/opal/mca/hwloc/base/hwloc_base_open.c +++ b/opal/mca/hwloc/base/hwloc_base_open.c @@ -96,7 +96,7 @@ int opal_hwloc_base_open(void) break; } mca_base_param_reg_string_name("hwloc", "base_mem_alloc_policy", - "Policy that determines how general memory allocations are bound 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.", + "Policy that determines how general memory allocations are placed after MPI_INIT (note that this is different than 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.", false, false, str_value, &str_value); if (strcasecmp(str_value, "none") == 0) { opal_hwloc_base_map = OPAL_HWLOC_BASE_MAP_NONE;