From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Shi Subject: Re: [RFC PATCH 1/3] mm: Drop locked from isolate_migratepages_block Date: Fri, 14 Aug 2020 15:25:11 +0800 Message-ID: References: <20200813035100.13054.25671.stgit@localhost.localdomain> <20200813040224.13054.96724.stgit@localhost.localdomain> <8ea9e186-b223-fb1b-5c82-2aa43c5e9f10@linux.alibaba.com> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: Sender: cgroups-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="utf-8" To: Alexander Duyck Cc: Yang Shi , kbuild test robot , Rong Chen , Konstantin Khlebnikov , "Kirill A. Shutemov" , Hugh Dickins , LKML , Daniel Jordan , linux-mm , Shakeel Butt , Matthew Wilcox , Johannes Weiner , Tejun Heo , cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Andrew Morton , Wei Yang , Mel Gorman , Joonsoo Kim 在 2020/8/13 下午10:32, Alexander Duyck 写道: >> Thanks a lot! >> Don't know if community is ok if we keep the patch following whole patchset alone? > I am fine with you squashing it with another patch if you want. In > theory this could probably be squashed in with the earlier patch I > submitted that introduced lruvec_holds_page_lru_lock or some other > patch. It is mostly just a cleanup anyway as it gets us away from > needing to hold the RCU read lock in the case that we already have the > correct lruvec. Hi Alexander, Thanks a lot! look like it's better to fold it in patch 17. Alex