[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7e0c2fe0-c867-3ea2-83a2-c3bcb35057d7@oracle.com>
Date: Wed, 12 Sep 2018 09:30:28 -0400
From: Daniel Jordan <daniel.m.jordan@...cle.com>
To: Laurent Dufour <ldufour@...ux.vnet.ibm.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, cgroups@...r.kernel.org
Cc: aaron.lu@...el.com, ak@...ux.intel.com, akpm@...ux-foundation.org,
dave.dice@...cle.com, dave.hansen@...ux.intel.com,
hannes@...xchg.org, levyossi@...oud.com,
mgorman@...hsingularity.net, mhocko@...nel.org,
Pavel.Tatashin@...rosoft.com, steven.sistare@...cle.com,
tim.c.chen@...el.com, vdavydov.dev@...il.com, ying.huang@...el.com
Subject: Re: [RFC PATCH v2 2/8] mm: make zone_reclaim_stat updates thread-safe
On 9/11/18 12:40 PM, Laurent Dufour wrote:
> On 11/09/2018 02:42, Daniel Jordan wrote:
>> diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
>> index 32699b2dc52a..6d4c23a3069d 100644
>> --- a/include/linux/mmzone.h
>> +++ b/include/linux/mmzone.h
>> @@ -229,6 +229,12 @@ struct zone_reclaim_stat {
>> *
>> * The anon LRU stats live in [0], file LRU stats in [1]
>> */
>> + atomic_long_t recent_rotated[2];
>> + atomic_long_t recent_scanned[2];
>
> It might be better to use a slightly different name for these fields to
> distinguish them from the ones in the zone_reclaim_stat_cpu structure.
Sure, these are now named recent_rotated_cpu and recent_scanned_cpu, absent better names.
Thanks for your comments.
Powered by blists - more mailing lists