[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6d2d215e-fd72-b8cc-331f-189ea04a361d@linux.alibaba.com>
Date: Thu, 12 Nov 2020 11:35:23 +0800
From: Alex Shi <alex.shi@...ux.alibaba.com>
To: Hugh Dickins <hughd@...gle.com>, Vlastimil Babka <vbabka@...e.cz>
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 v21 15/19] mm/compaction: do page isolation first in
compaction
在 2020/11/12 上午10:28, Hugh Dickins 写道:
>>> * Page become compound since the non-locked check,
>>> * and it's on LRU. It can only be a THP so the order
>>> @@ -990,16 +1002,13 @@ static bool too_many_isolated(pg_data_t *pgdat)
> Completely off-topic, and won't matter at all when Andrew rediffs into
> mmotm: but isn't it weird that this is showing "too_many_isolated(",
> when actually the function is isolate_migratepages_block()?
>
My git version is too low for this. Thanks for reminder. the latest git
work fine on correct function name.
Thanks
Powered by blists - more mailing lists