The patch titled
Subject: mm: print the correct method to disable automatic numa migration
has been added to the -mm tree. Its filename is
mm-print-the-correct-method-to-disable-automatic-numa-migration.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Andi Kleen <ak@xxxxxxxxxxxxxxx>
Subject: mm: print the correct method to disable automatic numa migration
When the "default y" CONFIG_NUMA_BALANCING_DEFAULT_ENABLED is enabled, the
message it prints refers to a sysctl to disable it again. But that sysctl
doesn't exist.
Document the correct (highly obscure method) through debugfs.
This should be also in Documentation/* but isn't.
Also fix the checkpatch problems.
BTW I think the "default y" is highly dubious for such a
experimential feature.
Signed-off-by: Andi Kleen <ak@xxxxxxxxxxxxxxx>
Cc: Mel Gorman <mel@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/mempolicy.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN mm/mempolicy.c~mm-print-the-correct-method-to-disable-automatic-numa-migration mm/mempolicy.c
--- a/mm/mempolicy.c~mm-print-the-correct-method-to-disable-automatic-numa-migration
+++ a/mm/mempolicy.c
@@ -2530,8 +2530,8 @@ static void __init check_numabalancing_e
numabalancing_default = true;
if (nr_node_ids > 1 && !numabalancing_override) {
- printk(KERN_INFO "Enabling automatic NUMA balancing. "
- "Configure with numa_balancing= or sysctl");
+ pr_info("Enabling automatic NUMA balancing.\n");
+ pr_info("Change with numa_balancing= or echo -NUMA >/sys/kernel/debug/sched_features\n");
set_numabalancing_state(numabalancing_default);
}
}
_
Patches currently in -mm which might be from ak@xxxxxxxxxxxxxxx are
linux-next.patch
mm-print-the-correct-method-to-disable-automatic-numa-migration.patch
lockdep-introduce-lock_acquire_exclusive-shared-helper-macros.patch
lglock-update-lockdep-annotations-to-report-recursive-local-locks.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
