From: Andi Kleen <andi@firstfloor.org>
To: Mel Gorman <mgorman@suse.de>
Cc: Andi Kleen <andi@firstfloor.org>,
akpm@linux-foundation.org, linux-mm@kvack.org,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] mm: Print the correct method to disable automatic numa migration
Date: Thu, 11 Apr 2013 16:04:25 +0200 [thread overview]
Message-ID: <20130411140425.GJ16732@two.firstfloor.org> (raw)
In-Reply-To: <20130411124803.GK3710@suse.de>
> As David pointed out, CONFIG_NUMA_BALANCING_DEFAULT_ENABLED only comes
> into play when CONFIG_NUMA_BALANCING is set and CONFIG_NUMA_BALANCING
> will default to N for make oldconfig. I think it's sensible to enable it
> by default if it's configured in.
I've got reports from users who got it unexpected and it messed
everything up for them.
>
> David has also already pointed out the problems with NO_NUMA vs -NUMA and
> the fact that the option only exists if CONFIG_SCHED_DEBUG which I agree
> is unfortunate. Ends up with this sort of mess
We just need the sysctl. Are you adding one or should I send
another patch with it?
BTW all the knobs are undocumented in Documentation/* too.
Please document any sysctl you submit.
Undocumented = may as well no exist.
-Andi
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-04-11 14:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 19:35 [PATCH] mm: Print the correct method to disable automatic numa migration Andi Kleen
2013-04-10 21:15 ` David Rientjes
2013-04-10 21:26 ` Andi Kleen
2013-04-10 21:29 ` David Rientjes
2013-04-11 12:48 ` Mel Gorman
2013-04-11 14:04 ` Andi Kleen [this message]
2013-04-11 14:19 ` Mel Gorman
2013-04-11 15:53 ` Andi Kleen
2013-04-11 17:25 ` Mel Gorman
2013-04-11 17:39 ` Andi Kleen
2013-04-11 17:48 ` Mel Gorman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130411140425.GJ16732@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.