All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: John Blackwood <john.blackwood@ccur.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [ PATCH ] Remove numa_balancing sysctl dependence on CONFIG_SCHED_DEBUG
Date: Tue, 23 Sep 2014 21:50:38 -0700	[thread overview]
Message-ID: <87d2al7hb5.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <5421B992.6050500@ccur.com> (John Blackwood's message of "Tue, 23 Sep 2014 13:18:58 -0500")

John Blackwood <john.blackwood@ccur.com> writes:

> numa: numa_balancing sysctl scope change
>
> Make the 'numa_balancing' sysctl parameter no longer dependent upon
> CONFIG_SCHED_DEBUG so it can be used in non-debug kernels.

Looks good.
-Andi

>
> Signed-off-by: John Blackwood <john.blackwood@ccur.com>
>
> Index: b/kernel/sysctl.c
> ===================================================================
> --- a/kernel/sysctl.c
> +++ b/kernel/sysctl.c
> @@ -389,6 +389,9 @@ static struct ctl_table kern_table[] = {
>  		.mode		= 0644,
>  		.proc_handler	= proc_dointvec,
>  	},
> +#endif /* CONFIG_NUMA_BALANCING */
> +#endif /* CONFIG_SCHED_DEBUG */
> +#ifdef CONFIG_NUMA_BALANCING
>  	{
>  		.procname	= "numa_balancing",
>  		.data		= NULL, /* filled in by handler */
> @@ -399,7 +402,6 @@ static struct ctl_table kern_table[] = {
>  		.extra2		= &one,
>  	},
>  #endif /* CONFIG_NUMA_BALANCING */
> -#endif /* CONFIG_SCHED_DEBUG */
>  	{
>  		.procname	= "sched_rt_period_us",
>  		.data		= &sysctl_sched_rt_period,

-- 
ak@linux.intel.com -- Speaking for myself only

      reply	other threads:[~2014-09-24  4:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23 18:18 [ PATCH ] Remove numa_balancing sysctl dependence on CONFIG_SCHED_DEBUG John Blackwood
2014-09-24  4:50 ` Andi Kleen [this message]

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=87d2al7hb5.fsf@tassilo.jf.intel.com \
    --to=andi@firstfloor.org \
    --cc=john.blackwood@ccur.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.