[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1bd90605-c765-ca27-b8ee-ca803a8bcdea@linux.intel.com>
Date: Sun, 17 Sep 2017 21:13:13 -0700
From: Dave Hansen <dave.hansen@...ux.intel.com>
To: kemi <kemi.wang@...el.com>, Michal Hocko <mhocko@...nel.org>
Cc: "Luis R . Rodriguez" <mcgrof@...nel.org>,
Kees Cook <keescook@...omium.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Jonathan Corbet <corbet@....net>,
Mel Gorman <mgorman@...hsingularity.net>,
Johannes Weiner <hannes@...xchg.org>,
Christopher Lameter <cl@...ux.com>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Vlastimil Babka <vbabka@...e.cz>,
Tim Chen <tim.c.chen@...el.com>,
Andi Kleen <andi.kleen@...el.com>,
Jesper Dangaard Brouer <brouer@...hat.com>,
Ying Huang <ying.huang@...el.com>,
Aaron Lu <aaron.lu@...el.com>,
Proc sysctl <linux-fsdevel@...r.kernel.org>,
Linux MM <linux-mm@...ck.org>,
Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/3] mm: Handle numa statistics distinctively based-on
different VM stats modes
On 09/17/2017 08:07 PM, kemi wrote:
>>> + if (vmstat_mode) {
>>> + if (vmstat_mode == VMSTAT_COARSE_MODE)
>>> + return;
>>> + } else if (disable_zone_statistics)
>>> + return;
>>> +
>>> if (z->node != numa_node_id())
>>> local_stat = NUMA_OTHER;
>>
>> A jump label could make this completely out of the way for the case
>> where every single cycle matters.
>
> Could you be more explicit for how to implement it here. Thanks very much.
Take a look at include/linux/jump_label.h.
Powered by blists - more mailing lists