[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bf8be185-e757-cf05-999d-56bfb83f1bc9@linux.alibaba.com>
Date: Tue, 20 Aug 2019 22:21:39 +0800
From: Alex Shi <alex.shi@...ux.alibaba.com>
To: Matthew Wilcox <willy@...radead.org>
Cc: cgroups@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>,
Mel Gorman <mgorman@...hsingularity.net>,
Tejun Heo <tj@...nel.org>, Jason Gunthorpe <jgg@...pe.ca>,
Dan Williams <dan.j.williams@...el.com>,
Vlastimil Babka <vbabka@...e.cz>,
Ira Weiny <ira.weiny@...el.com>,
Jesper Dangaard Brouer <brouer@...hat.com>,
Andrey Ryabinin <aryabinin@...tuozzo.com>,
Jann Horn <jannh@...gle.com>,
Logan Gunthorpe <logang@...tatee.com>,
Souptick Joarder <jrdr.linux@...il.com>,
Ralph Campbell <rcampbell@...dia.com>,
"Tobin C. Harding" <tobin@...nel.org>,
Michal Hocko <mhocko@...e.com>,
Oscar Salvador <osalvador@...e.de>,
Wei Yang <richard.weiyang@...il.com>,
Johannes Weiner <hannes@...xchg.org>,
Pavel Tatashin <pasha.tatashin@...cle.com>,
Arun KS <arunks@...eaurora.org>,
"Darrick J. Wong" <darrick.wong@...cle.com>,
Amir Goldstein <amir73il@...il.com>,
Dave Chinner <dchinner@...hat.com>,
Josef Bacik <josef@...icpanda.com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Jérôme Glisse <jglisse@...hat.com>,
Mike Kravetz <mike.kravetz@...cle.com>,
Hugh Dickins <hughd@...gle.com>,
Kirill Tkhai <ktkhai@...tuozzo.com>,
Daniel Jordan <daniel.m.jordan@...cle.com>,
Yafang Shao <laoar.shao@...il.com>,
Yang Shi <yang.shi@...ux.alibaba.com>
Subject: Re: [PATCH 14/14] mm/lru: fix the comments of lru_lock
在 2019/8/20 下午10:00, Matthew Wilcox 写道:
> On Tue, Aug 20, 2019 at 05:48:37PM +0800, Alex Shi wrote:
>> @@ -159,7 +159,7 @@ static inline bool free_area_empty(struct free_area *area, int migratetype)
>> struct pglist_data;
>>
>> /*
>> - * zone->lock and the zone lru_lock are two of the hottest locks in the kernel.
>> + * zone->lock and the lru_lock are two of the hottest locks in the kernel.
>> * So add a wild amount of padding here to ensure that they fall into separate
>> * cachelines. There are very few zone structures in the machine, so space
>> * consumption is not a concern here.
>
> But after this patch series, the lru lock is no longer stored in the zone.
> So this comment makes no sense.
Yes, It's need reconsider here. thanks for opoint out.
>
>> @@ -295,7 +295,7 @@ struct zone_reclaim_stat {
>>
>> struct lruvec {
>> struct list_head lists[NR_LRU_LISTS];
>> - /* move lru_lock to per lruvec for memcg */
>> + /* perf lruvec lru_lock for memcg */
>
> What does the word 'perf' mean here?
sorry for typo, could be s/perf/per/ here.
Thanks
Alex
Powered by blists - more mailing lists