[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8ea9e186-b223-fb1b-5c82-2aa43c5e9f10@linux.alibaba.com>
Date: Thu, 13 Aug 2020 14:56:30 +0800
From: Alex Shi <alex.shi@...ux.alibaba.com>
To: Alexander Duyck <alexander.duyck@...il.com>
Cc: yang.shi@...ux.alibaba.com, lkp@...el.com, rong.a.chen@...el.com,
khlebnikov@...dex-team.ru, kirill@...temov.name, hughd@...gle.com,
linux-kernel@...r.kernel.org, daniel.m.jordan@...cle.com,
linux-mm@...ck.org, shakeelb@...gle.com, willy@...radead.org,
hannes@...xchg.org, tj@...nel.org, cgroups@...r.kernel.org,
akpm@...ux-foundation.org, richard.weiyang@...il.com,
mgorman@...hsingularity.net, iamjoonsoo.kim@....com
Subject: Re: [RFC PATCH 1/3] mm: Drop locked from isolate_migratepages_block
在 2020/8/13 下午12:02, Alexander Duyck 写道:
> From: Alexander Duyck <alexander.h.duyck@...ux.intel.com>
>
> We can drop the need for the locked variable by making use of the
> lruvec_holds_page_lru_lock function. By doing this we can avoid some rcu
> locking ugliness for the case where the lruvec is still holding the LRU
> lock associated with the page. Instead we can just use the lruvec and if it
> is NULL we assume the lock was released.
>
> Signed-off-by: Alexander Duyck <alexander.h.duyck@...ux.intel.com>
> ---
> mm/compaction.c | 45 ++++++++++++++++++++-------------------------
> 1 file changed, 20 insertions(+), 25 deletions(-)
Thanks a lot!
Don't know if community is ok if we keep the patch following whole patchset alone?
Powered by blists - more mailing lists