Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752095AbcCGG34 (ORCPT ); Mon, 7 Mar 2016 01:29:56 -0500 Received: from TYO201.gate.nec.co.jp ([210.143.35.51]:33920 "EHLO tyo201.gate.nec.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752023AbcCGG3s convert rfc822-to-8bit (ORCPT ); Mon, 7 Mar 2016 01:29:48 -0500 From: Naoya Horiguchi To: Balbir Singh CC: "linux-mm@kvack.org" , "Kirill A. Shutemov" , Hugh Dickins , "Andrew Morton" , Dave Hansen , Andrea Arcangeli , Mel Gorman , Michal Hocko , "Vlastimil Babka" , Pavel Emelyanov , "linux-kernel@vger.kernel.org" , "Naoya Horiguchi" Subject: Re: [PATCH v1 02/11] mm: thp: introduce CONFIG_ARCH_ENABLE_HUGEPAGE_MIGRATION Thread-Topic: [PATCH v1 02/11] mm: thp: introduce CONFIG_ARCH_ENABLE_HUGEPAGE_MIGRATION Thread-Index: AQHRdSAzgyBZIsY1k0mVFcl0zH0kqJ9Ml64AgABcboA= Date: Mon, 7 Mar 2016 06:28:54 +0000 Message-ID: <20160307062853.GA31458@hori1.linux.bs1.fc.nec.co.jp> References: <1456990918-30906-1-git-send-email-n-horiguchi@ah.jp.nec.com> <1456990918-30906-3-git-send-email-n-horiguchi@ah.jp.nec.com> <20160307005804.GA25148@cotter.ozlabs.ibm.com> In-Reply-To: <20160307005804.GA25148@cotter.ozlabs.ibm.com> Accept-Language: ja-JP, en-US Content-Language: ja-JP X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.128.101.32] Content-Type: text/plain; charset="iso-2022-jp" Content-ID: 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: 1091 Lines: 22 On Mon, Mar 07, 2016 at 11:58:04AM +1100, Balbir Singh wrote: > On Thu, Mar 03, 2016 at 04:41:49PM +0900, Naoya Horiguchi wrote: > > Introduces CONFIG_ARCH_ENABLE_HUGEPAGE_MIGRATION to limit thp migration > > functionality to x86_64, which should be safer at the first step. > > > > The changelog is not helpful. Could you please describe what is > architecture specific in these changes? What do other arches need to do > to port these changes over? The arch specific parts are pmd_present() and swap entry format. Currently pmd_present() in x86_64 is not simple enough to easily determine pmd's state (none, normal pmd entry pointing to pte page, pmd for thp, or pmd migration entry ...) That requires me to assume in this version that pmd migration entry should have_PAGE_PSE set, which should not be necessary if the complexity is fixed. So I will mention this pmd_present() problem in the next version. So if it's fixed, what developers need to do to port this feature to their architectures is just to enable CONFIG_ARCH_ENABLE_THP_MIGRATION (and test it.) Thanks, Naoya Horiguchi