From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-x241.google.com (mail-oi0-x241.google.com [IPv6:2607:f8b0:4003:c06::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id C33AF21B02822 for ; Wed, 12 Sep 2018 09:50:35 -0700 (PDT) Received: by mail-oi0-x241.google.com with SMTP id l82-v6so5048579oih.11 for ; Wed, 12 Sep 2018 09:50:35 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <20180910232615.4068.29155.stgit@localhost.localdomain> <20180910234354.4068.65260.stgit@localhost.localdomain> <7b96298e-9590-befd-0670-ed0c9fcf53d5@microsoft.com> From: Dan Williams Date: Wed, 12 Sep 2018 09:50:34 -0700 Message-ID: Subject: Re: [PATCH 3/4] mm: Defer ZONE_DEVICE page initialization to the point where we init pgmap List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Alexander Duyck Cc: Pavel.Tatashin@microsoft.com, Michal Hocko , linux-nvdimm , Dave Hansen , LKML , linux-mm , =?UTF-8?B?SsOpcsO0bWUgR2xpc3Nl?= , Andrew Morton , Ingo Molnar , "Kirill A. Shutemov" List-ID: On Wed, Sep 12, 2018 at 8:48 AM, Alexander Duyck wrote: > On Wed, Sep 12, 2018 at 6:59 AM Pasha Tatashin > wrote: >> >> Hi Alex, > > Hi Pavel, > >> Please re-base on linux-next, memmap_init_zone() has been updated there >> compared to mainline. You might even find a way to unify some parts of >> memmap_init_zone and memmap_init_zone_device as memmap_init_zone() is a >> lot simpler now. > > This patch applied to the linux-next tree with only a little bit of > fuzz. It looks like it is mostly due to some code you had added above > the function as well. I have updated this patch so that it will apply > to both linux and linux-next by just moving the new function to > underneath memmap_init_zone instead of above it. > >> I think __init_single_page() should stay local to page_alloc.c to keep >> the inlining optimization. > > I agree. In addition it will make pulling common init together into > one space easier. I would rather not have us create an opportunity for > things to further diverge by making it available for anybody to use. I'll buy the inline argument for keeping the new routine in page_alloc.c, but I otherwise do not see the divergence danger or "making __init_single_page() available for anybody" given the the declaration is limited in scope to a mm/ local header file. _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm