From patchwork Thu Sep 20 22:24:09 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Alexander Duyck X-Patchwork-Id: 10608795 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id 2E4EC15A6 for ; Thu, 20 Sep 2018 22:24:23 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 19A4C2DEE6 for ; Thu, 20 Sep 2018 22:24:23 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id 0D8602DF06; Thu, 20 Sep 2018 22:24:23 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=2.0 tests=BAYES_00,MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 Received: from ml01.01.org (ml01.01.org [198.145.21.10]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.wl.linuxfoundation.org (Postfix) with ESMTPS id 9C7892DEE6 for ; Thu, 20 Sep 2018 22:24:22 +0000 (UTC) Received: from [127.0.0.1] (localhost [IPv6:::1]) by ml01.01.org (Postfix) with ESMTP id 6930A21148ECF; Thu, 20 Sep 2018 15:24:22 -0700 (PDT) X-Original-To: linux-nvdimm@lists.01.org Delivered-To: linux-nvdimm@lists.01.org Received-SPF: None (no SPF record) identity=mailfrom; client-ip=192.55.52.88; helo=mga01.intel.com; envelope-from=alexander.h.duyck@linux.intel.com; receiver=linux-nvdimm@lists.01.org Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 2F7EC21148ECD for ; Thu, 20 Sep 2018 15:24:21 -0700 (PDT) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Sep 2018 15:24:20 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,282,1534834800"; d="scan'208";a="85285084" Received: from ahduyck-mobl.amr.corp.intel.com (HELO localhost.localdomain) ([10.7.198.152]) by orsmga003.jf.intel.com with ESMTP; 20 Sep 2018 15:24:10 -0700 Subject: [PATCH v4 0/5] Address issues slowing persistent memory initialization From: Alexander Duyck To: linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-nvdimm@lists.01.org Date: Thu, 20 Sep 2018 15:24:09 -0700 Message-ID: <20180920215824.19464.8884.stgit@localhost.localdomain> User-Agent: StGit/0.17.1-dirty MIME-Version: 1.0 X-BeenThere: linux-nvdimm@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Linux-nvdimm developer list." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: pavel.tatashin@microsoft.com, mhocko@suse.com, dave.hansen@intel.com, jglisse@redhat.com, akpm@linux-foundation.org, mingo@kernel.org, kirill.shutemov@linux.intel.com Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" X-Virus-Scanned: ClamAV using ClamSMTP This patch set is meant to be a v4 to my earlier patch set "Address issues slowing memory init"[1], and a follow-up to my earlier patch set "Address issues slowing persistent memory initialization"[2]. Excluding any gains seen from using the vm_debug option to disable page init poisoning I see a total reduction in file-system init time of about two and a half minutes, or 65%, for a system initializing btrfs on a 12TB block of persistent memory split evenly over 4 NUMA nodes. Since the last patch set I have reworked the first patch to provide a more generic disable implementation that can be extended in the future. I tweaked the commit message for the second patch slightly to reflect why we might want to use a non-atomic __set_bit versus the atomic set_bit. I have modified the third patch to make it so that it can merge onto either the linux git tree or the linux-next git tree. The patch set that Dan Williams has outstanding may end up conflicting with this patch depending on the merge order. If his are merged first I believe the code I changed in mm/hmm.c could be dropped entirely. The fourth patch has been split into two and focused more on the async scheduling portion of the nvdimm code. The result is much cleaner than the original approach in that instead of having two threads running we are now getting the thread running where we wanted it to be. The last change for all patches is that I have updated my email address to alexander.h.duyck@linux.intel.com to reflect the fact that I have changed teams within Intel. I will be trying to use that for correspondence going forward instead of my gmail account. [1]: https://lkml.org/lkml/2018/9/5/924 [2]: https://lkml.org/lkml/2018/9/11/10 [3]: https://lkml.org/lkml/2018/9/13/104 --- Alexander Duyck (5): mm: Provide kernel parameter to allow disabling page init poisoning mm: Create non-atomic version of SetPageReserved for init use mm: Defer ZONE_DEVICE page initialization to the point where we init pgmap async: Add support for queueing on specific node nvdimm: Schedule device registration on node local to the device Documentation/admin-guide/kernel-parameters.txt | 12 +++ drivers/nvdimm/bus.c | 19 ++++ include/linux/async.h | 20 ++++- include/linux/mm.h | 2 include/linux/page-flags.h | 9 ++ kernel/async.c | 36 ++++++-- kernel/memremap.c | 24 ++--- mm/debug.c | 46 ++++++++++ mm/hmm.c | 12 ++- mm/memblock.c | 5 - mm/page_alloc.c | 101 ++++++++++++++++++++++- mm/sparse.c | 4 - 12 files changed, 243 insertions(+), 47 deletions(-) --