From: Dave Hansen <dave.hansen@linux.intel.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: kemi <kemi.wang@intel.com>,
"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>, 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>,
Aaron Lu <aaron.lu@intel.com>
Subject: Re: [PATCH v3] mm, sysctl: make NUMA stats configurable
Date: Tue, 10 Oct 2017 08:39:47 -0700 [thread overview]
Message-ID: <4949ccef-6b7f-c2d6-f500-92eadb2ba649@linux.intel.com> (raw)
In-Reply-To: <20171010145728.q2levvekbpwlg57q@dhcp22.suse.cz>
On 10/10/2017 07:57 AM, Michal Hocko wrote:
>> But, let's be honest, this leaves us with an option that nobody is ever
>> going to turn on. IOW, nobody except a very small portion of our users
>> will ever see any benefit from this.
> But aren't those small groups who would like to squeeze every single
> cycle out from the page allocator path the targeted audience?
They're the reason we started looking at this. They also care the most.
But, the cost of these stats, especially we get more and more cores in a
NUMA node is really making them show up in profiles. It would be nice
to get rid of them there, too.
Aaron, do you remember offhand how much of the allocator overhead was
coming from NUMA stats?
--
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-10 15:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 6:11 [PATCH v3] mm, sysctl: make NUMA stats configurable Kemi Wang
2017-09-28 21:29 ` Andrew Morton
2017-09-29 1:44 ` kemi
2017-09-29 7:09 ` Vlastimil Babka
2017-09-29 7:03 ` Vlastimil Babka
2017-10-09 2:20 ` kemi
2017-09-29 7:27 ` Vlastimil Babka
2017-10-03 9:23 ` Michal Hocko
2017-10-09 6:34 ` kemi
2017-10-09 7:55 ` Michal Hocko
2017-10-10 5:49 ` Michal Hocko
2017-10-10 5:54 ` kemi
2017-10-10 14:29 ` Dave Hansen
2017-10-10 14:31 ` Michal Hocko
2017-10-10 14:53 ` Dave Hansen
2017-10-10 14:57 ` Michal Hocko
2017-10-10 15:14 ` Christopher Lameter
2017-10-10 15:39 ` Dave Hansen [this message]
2017-10-10 17:51 ` Michal Hocko
2017-10-10 21:34 ` Andrew Morton
2017-10-11 6:16 ` Vlastimil Babka
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=4949ccef-6b7f-c2d6-f500-92eadb2ba649@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=aaron.lu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi.kleen@intel.com \
--cc=bigeasy@linutronix.de \
--cc=brouer@redhat.com \
--cc=cl@linux.com \
--cc=corbet@lwn.net \
--cc=hannes@cmpxchg.org \
--cc=keescook@chromium.org \
--cc=kemi.wang@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).