Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756451AbcK2IVz convert rfc822-to-8bit (ORCPT ); Tue, 29 Nov 2016 03:21:55 -0500 Received: from TYO202.gate.nec.co.jp ([210.143.35.52]:49982 "EHLO tyo202.gate.nec.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754364AbcK2IVs (ORCPT ); Tue, 29 Nov 2016 03:21:48 -0500 From: Naoya Horiguchi To: Michal Hocko CC: "linux-mm@kvack.org" , "Kirill A. Shutemov" , Hugh Dickins , "Andrew Morton" , Dave Hansen , Andrea Arcangeli , Mel Gorman , Vlastimil Babka , "Pavel Emelyanov" , Zi Yan , Balbir Singh , "linux-kernel@vger.kernel.org" , Naoya Horiguchi Subject: Re: [PATCH v2 06/12] mm: thp: enable thp migration in generic path Thread-Topic: [PATCH v2 06/12] mm: thp: enable thp migration in generic path Thread-Index: AQHSOVlb5iz7umLMGUytFzp3OvqHjaDt/zYAgAEo4oA= Date: Tue, 29 Nov 2016 08:16:08 +0000 Message-ID: <20161129081607.GC15582@hori1.linux.bs1.fc.nec.co.jp> References: <1478561517-4317-1-git-send-email-n-horiguchi@ah.jp.nec.com> <1478561517-4317-7-git-send-email-n-horiguchi@ah.jp.nec.com> <20161128143331.GO14788@dhcp22.suse.cz> In-Reply-To: <20161128143331.GO14788@dhcp22.suse.cz> Accept-Language: en-US, ja-JP Content-Language: ja-JP X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.128.101.15] Content-Type: text/plain; charset="iso-2022-jp" Content-ID: <1650E9A2E016004B8CA537B0D06B1EB9@gisp.nec.co.jp> Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 792 Lines: 17 On Mon, Nov 28, 2016 at 03:33:32PM +0100, Michal Hocko wrote: > On Tue 08-11-16 08:31:51, Naoya Horiguchi wrote: > > This patch makes it possible to support thp migration gradually. If you fail > > to allocate a destination page as a thp, you just split the source thp as we > > do now, and then enter the normal page migration. If you succeed to allocate > > destination thp, you enter thp migration. Subsequent patches actually enable > > thp migration for each caller of page migration by allowing its get_new_page() > > callback to allocate thps. > > Does this need to be in a separate patch? Wouldn't it make more sense to > have the full THP migration code in a single one? Actually, no big reason for separate patch. So I'm OK to merge this into patch 5/12. Thanks, Naoya Horiguchi