Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp3206543imm; Mon, 10 Sep 2018 12:48:39 -0700 (PDT) X-Google-Smtp-Source: ANB0VdaYRKKaUxbdZey/ExXYE/+/WYhr8ZgRLRPEcEFrHBfWOvzkYsu8QJjspp/wf5qW4ovHTc7E X-Received: by 2002:a17:902:a987:: with SMTP id bh7-v6mr24032343plb.182.1536608919078; Mon, 10 Sep 2018 12:48:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536608919; cv=none; d=google.com; s=arc-20160816; b=f/xkA4MKb9U2PZFoK/++yXp6EWSVDolbT93xAs11qYJFyVQZmPuaEIMyFQXd/EYltH nA/clFpsFXUvWKXpYyMCYs95MwuhCWDYKzObKesZrZFoAjoly7povMPHHYBEqbF8bdAg Zg8YZ5XA92eh3G1pZCoYhUNmIhv5eyp+NyV29N1hbicIofDaQ8Vrcd1uuiDlMZXIp3fK MgjRJUq/ff7XGebdBPms8oN+6Y6rbfTMrrIDCSP4TPvAk0eN9Lp2RblEDIUf3nSZd2bj sYv8l/yDfAhvI/6Ljm+9N+ZuZSa9HkyLN9d+jb6k9Z+cYCaJKzut8+JorIvKQUKhH2X5 7QRA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=6Ol/OhBtansvJU+w61mQSjhKetBbCopAEatwEP6lj2s=; b=CHBh6xIWiXNEw9BR/Z0dJaRRe1QSv+VzfeAm3Kouc1rPhN3Cj+QX3a/XC5jryyX8UI YTpy2kreFVAIfk+stFH8h5ca/MkyGycSfIXgwg5QKdJUewbyzgp6VLnJ/kRiKYy7/JlZ D9uNLqM5c5QBW9fArxyq8tpdI9llTf+4HL+8j/MT6kFQbaHFC4qgQQVNjx8QqimKEqs0 VOIOl+9LCZ6SnQMI8JmLP3I/6ndEo7oKbiDJhvk1PL7QhKzwIDMNViZ4NCk1YzeatXcs ZeCy30Bojc8+JDjWjkWy6qkA3+ag94bUollTGt3v8WEyisRnIBc4qsjp6t6ud5h+Gnyk ARww== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=HfmI4uKg; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k1-v6si17233563pgh.65.2018.09.10.12.48.15; Mon, 10 Sep 2018 12:48:39 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=HfmI4uKg; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728869AbeIKAnr (ORCPT + 99 others); Mon, 10 Sep 2018 20:43:47 -0400 Received: from mail-io0-f195.google.com ([209.85.223.195]:42594 "EHLO mail-io0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728153AbeIKAnr (ORCPT ); Mon, 10 Sep 2018 20:43:47 -0400 Received: by mail-io0-f195.google.com with SMTP id n18-v6so1650635ioa.9 for ; Mon, 10 Sep 2018 12:48:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6Ol/OhBtansvJU+w61mQSjhKetBbCopAEatwEP6lj2s=; b=HfmI4uKgwhLH28jgbzF2ORI3MlqNimNy2ILNFfMxzoYlfbXDmBohlyx6G25XBZXjPG /NMugZd06EuZM2wSDJxY8QKvuv8pL7VXQh4KsQ1DJZpY0BfZ9s3OoqlUqEZ4AWRzqa+o D6Zt+XkZ4qZ3BbcF5eT9A9qxcPkEx0AF6fe5p/7KtHB4U8w6kCYlofryc6He77IzlP6u +8v5xXDQ2vbSEkcvGwoC9hbc2ZLWgR3uzXWRlXdX2kTg5M5J1kAZ6ivt+N+o9jobrr2O CsAMNzlp+XY8PGmidXSvYUfG9FJhV4/eWDpkfjxnZvojm+4z1y877OrmUvhSwL+zE2b9 Gw1A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6Ol/OhBtansvJU+w61mQSjhKetBbCopAEatwEP6lj2s=; b=lBMhAylD2YdsBWCSBKyEx7/fYFpNtHWSIRZaSzmEq3kC5sxSxBT2Po4E2fVp3k/Rj7 k0wzHB8bNZ1zPHUEMPIlOQw5RMNDy8dxoTJ0NcBZmTc6OpjDa1+NMSm1qscyhakC3MnT 9YKVkyiYN3G6865Rv8Cp94TI2lDVkwImdovJuQNOoyEiWzJwurYdLapipolGoEE7Nh9R q9f2ZLrTfRCz5Gp9+LrtDVcdLIkSkyOknEHG4KJrQIgC8CzEHAzgc/22Uu/d6GMAFi2y f4t5x0WHXI2gjNfgWtow22/tMdmhZwl9r6hvBkJU/bbdltWcBiZr+ZM6bg13abHWigDa bYVQ== X-Gm-Message-State: APzg51CTa9NklJKU5UJGHu2onjoco8ARj/ocpNL4nc5DLxugRycyKspb 9qJoj736mI7r1A1YYMovSUnntfphMPLesSxaemQ= X-Received: by 2002:a6b:cac3:: with SMTP id a186-v6mr17978218iog.116.1536608887010; Mon, 10 Sep 2018 12:48:07 -0700 (PDT) MIME-Version: 1.0 References: <153176041838.12695.3365448145295112857.stgit@dwillia2-desk3.amr.corp.intel.com> <20180717155006.GL7193@dhcp22.suse.cz> <20180718120529.GY7193@dhcp22.suse.cz> <3f43729d-fd4e-a488-e04d-026ef5a28dd9@intel.com> <20180723110928.GC31229@dhcp22.suse.cz> <510a1213-e391-bad6-4239-60fa477aaac0@intel.com> <20180724072937.GD28386@dhcp22.suse.cz> In-Reply-To: From: Alexander Duyck Date: Mon, 10 Sep 2018 12:47:55 -0700 Message-ID: Subject: Re: [PATCH v2 00/14] mm: Asynchronous + multithreaded memmap init for ZONE_DEVICE To: dan.j.williams@intel.com Cc: mhocko@kernel.org, Dave Hansen , Pavel Tatashin , dalias@libc.org, jack@suse.cz, Benjamin Herrenschmidt , Heiko Carstens , linux-mm , Paul Mackerras , Peter Anvin , ysato@users.sourceforge.jp, linux-nvdimm@lists.01.org, "the arch/x86 maintainers" , Matthew Wilcox , Daniel Jordan , Ingo Molnar , fenghua.yu@intel.com, jglisse@redhat.com, Thomas Gleixner , Tony Luck , LKML , mpe@ellerman.id.au, Martin Schwidefsky , Andrew Morton , Christoph Hellwig , "Duyck, Alexander H" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Sep 10, 2018 at 12:06 PM Dan Williams wrote: > > [ adding Alex ] > > On Tue, Jul 24, 2018 at 12:29 AM, Michal Hocko wrote: > > On Mon 23-07-18 09:15:32, Dave Hansen wrote: > >> On 07/23/2018 04:09 AM, Michal Hocko wrote: > >> > On Thu 19-07-18 11:41:10, Dave Hansen wrote: > >> >> Are you looking for the actual end-user reports? This was more of a > >> >> case of the customer plugging in some persistent memory DIMMs, noticing > >> >> the boot delta and calling the folks who sold them the DIMMs (Intel). > >> > But this doesn't sound like something to rush a solution for in the > >> > upcoming merge windown, does it? > >> > >> No, we should not rush it. We'll try to rework it properly. > > > > Thanks a lot Dave! I definitely do not mean to block this at all. I just > > really do not like to have the code even more cluttered than we have > > now. > > Hi Michal, > > I'm back from vacation. I owe you an apology I was entirely too > prickly on this thread, and the vacation cool-off-time was much > needed. > > I come back to see that Alex has found a trove of low hanging fruit to > speed up ZONE_DEVICE init and ditch most of the complication I was > pushing. I'll let him chime in on the direction he wants to take this. The basic plan I have for now will basically replace the entire set-up with just 2 patches that would build on the 2 patches I had submitted earlier. One is a patch to the libnvdimm code to make it so that the probe routine NUMA aware similar to what is done in pci_call_probe. All of the async bits necessary were already contained in the libnvdimm code anyway. Ideally I need to probably look at following up with adding some NUMA awareness to the async_schedule_domain function. The second is actually pretty simple. Instead of moving the setting of the pgmap into memmap_init_zone we instead create a new function to take care of setting the pgmap and include the functionality from memmap_init_zone. The boundary between what is initialized and what isn't is where we start replacing the LRU list pointers with pgmap and hmm_data. I might try to send them out as an RFC later today to get everyone's thoughts. Thanks. - Alex