[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dfc21f50-998f-a9b7-4ab9-3598c32d7e49@linux.alibaba.com>
Date: Tue, 22 Sep 2020 11:38:22 +0800
From: Alex Shi <alex.shi@...ux.alibaba.com>
To: Hugh Dickins <hughd@...gle.com>
Cc: akpm@...ux-foundation.org, mgorman@...hsingularity.net,
tj@...nel.org, khlebnikov@...dex-team.ru,
daniel.m.jordan@...cle.com, willy@...radead.org,
hannes@...xchg.org, lkp@...el.com, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, cgroups@...r.kernel.org,
shakeelb@...gle.com, iamjoonsoo.kim@....com,
richard.weiyang@...il.com, kirill@...temov.name,
alexander.duyck@...il.com, rong.a.chen@...el.com, mhocko@...e.com,
vdavydov.dev@...il.com, shy828301@...il.com
Subject: Re: [PATCH v18 15/32] mm/lru: move lock into lru_note_cost
在 2020/9/22 上午5:36, Hugh Dickins 写道:
>
>> We have to move lru_lock into lru_note_cost, since it cycle up on memcg
>> tree, for future per lruvec lru_lock replace. It's a bit ugly and may
>> cost a bit more locking, but benefit from multiple memcg locking could
>> cover the lost.
>>
>> Signed-off-by: Alex Shi <alex.shi@...ux.alibaba.com>
> Acked-by: Hugh Dickins <hughd@...gle.com>
Thanks!
Powered by blists - more mailing lists