From: kemi <kemi.wang@intel.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: "Luis R . Rodriguez" <mcgrof@kernel.org>,
Kees Cook <keescook@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>,
Mel Gorman <mgorman@techsingularity.net>,
Johannes Weiner <hannes@cmpxchg.org>,
Christopher Lameter <cl@linux.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Vlastimil Babka <vbabka@suse.cz>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Dave <dave.hansen@linux.intel.com>,
Tim Chen <tim.c.chen@intel.com>,
Andi Kleen <andi.kleen@intel.com>,
Jesper Dangaard Brouer <brouer@redhat.com>,
Ying Huang <ying.huang@intel.com>, Aaron Lu <aaron.lu@intel.com>,
Proc sysctl <linux-fsdevel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>
Subject: Re: [PATCH v4] mm, sysctl: make NUMA stats configurable
Date: Tue, 17 Oct 2017 16:03:44 +0800 [thread overview]
Message-ID: <7103ce83-358e-2dfb-7880-ac2faea158f1@intel.com> (raw)
In-Reply-To: <20171017075420.dege7aabzau5wrss@dhcp22.suse.cz>
On 2017a1'10ae??17ae?JPY 15:54, Michal Hocko wrote:
> On Tue 17-10-17 09:20:58, Kemi Wang wrote:
> [...]
>
> Other than two remarks below, it looks good to me and it also looks
> simpler.
>
>> diff --git a/mm/vmstat.c b/mm/vmstat.c
>> index 4bb13e7..e746ed1 100644
>> --- a/mm/vmstat.c
>> +++ b/mm/vmstat.c
>> @@ -32,6 +32,76 @@
>>
>> #define NUMA_STATS_THRESHOLD (U16_MAX - 2)
>>
>> +#ifdef CONFIG_NUMA
>> +int sysctl_vm_numa_stat = ENABLE_NUMA_STAT;
>> +static DEFINE_MUTEX(vm_numa_stat_lock);
>
> You can scope this mutex to the sysctl handler function
>
OK, thanks.
>> +int sysctl_vm_numa_stat_handler(struct ctl_table *table, int write,
>> + void __user *buffer, size_t *length, loff_t *ppos)
>> +{
>> + int ret, oldval;
>> +
>> + mutex_lock(&vm_numa_stat_lock);
>> + if (write)
>> + oldval = sysctl_vm_numa_stat;
>> + ret = proc_dointvec(table, write, buffer, length, ppos);
>> + if (ret || !write)
>> + goto out;
>> +
>> + if (oldval == sysctl_vm_numa_stat)
>> + goto out;
>> + else if (oldval == DISABLE_NUMA_STAT) {
>
> So basically any value will enable numa stats. This means that we would
> never be able to extend this interface to e.g. auto mode (say value 2).
> I guess you meant to check sysctl_vm_numa_stat == ENABLE_NUMA_STAT?
>
I meant to make it more general other than ENABLE_NUMA_STAT(non 0 is enough),
but it will make it hard to scale, as you said.
So, it would be like this:
0 -- disable
1 -- enable
other value is invalid.
May add option 2 later for auto if necessary:)
>> + static_branch_enable(&vm_numa_stat_key);
>> + pr_info("enable numa statistics\n");
>> + } else if (sysctl_vm_numa_stat == DISABLE_NUMA_STAT) {
>> + static_branch_disable(&vm_numa_stat_key);
>> + invalid_numa_statistics();
>> + pr_info("disable numa statistics, and clear numa counters\n");
>> + }
>> +
>> +out:
>> + mutex_unlock(&vm_numa_stat_lock);
>> + return ret;
>> +}
>> +#endif
>> +
>> #ifdef CONFIG_VM_EVENT_COUNTERS
>> DEFINE_PER_CPU(struct vm_event_state, vm_event_states) = {{0}};
>> EXPORT_PER_CPU_SYMBOL(vm_event_states);
>> --
>> 2.7.4
>>
>
--
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:[~2017-10-17 8:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 1:20 Kemi Wang
2017-10-17 7:54 ` Michal Hocko
2017-10-17 8:03 ` kemi [this message]
2017-10-17 8:14 ` Michal Hocko
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=7103ce83-358e-2dfb-7880-ac2faea158f1@intel.com \
--to=kemi.wang@intel.com \
--cc=aaron.lu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi.kleen@intel.com \
--cc=aryabinin@virtuozzo.com \
--cc=bigeasy@linutronix.de \
--cc=brouer@redhat.com \
--cc=cl@linux.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=hannes@cmpxchg.org \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=tim.c.chen@intel.com \
--cc=vbabka@suse.cz \
--cc=ying.huang@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox