From: Alexander Duyck <alexander.h.duyck@linux.intel.com> To: linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-nvdimm@lists.01.org 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 Subject: [PATCH v4 0/5] Address issues slowing persistent memory initialization Date: Thu, 20 Sep 2018 15:24:09 -0700 [thread overview] Message-ID: <20180920215824.19464.8884.stgit@localhost.localdomain> (raw) 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(-) -- _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Duyck <alexander.h.duyck@linux.intel.com> To: linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-nvdimm@lists.01.org Cc: pavel.tatashin@microsoft.com, mhocko@suse.com, dave.jiang@intel.com, mingo@kernel.org, dave.hansen@intel.com, jglisse@redhat.com, akpm@linux-foundation.org, logang@deltatee.com, dan.j.williams@intel.com, kirill.shutemov@linux.intel.com Subject: [PATCH v4 0/5] Address issues slowing persistent memory initialization Date: Thu, 20 Sep 2018 15:24:09 -0700 [thread overview] Message-ID: <20180920215824.19464.8884.stgit@localhost.localdomain> (raw) 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(-) --
next reply other threads:[~2018-09-20 22:24 UTC|newest] Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-09-20 22:24 Alexander Duyck [this message] 2018-09-20 22:24 ` [PATCH v4 0/5] Address issues slowing persistent memory initialization Alexander Duyck 2018-09-20 22:26 ` [PATCH v4 1/5] mm: Provide kernel parameter to allow disabling page init poisoning Alexander Duyck 2018-09-20 22:26 ` Alexander Duyck 2018-09-21 19:04 ` Pasha Tatashin 2018-09-21 19:41 ` Logan Gunthorpe 2018-09-21 19:41 ` Logan Gunthorpe 2018-09-21 19:52 ` Pasha Tatashin 2018-09-20 22:27 ` [PATCH v4 2/5] mm: Create non-atomic version of SetPageReserved for init use Alexander Duyck 2018-09-20 22:27 ` Alexander Duyck 2018-09-21 19:06 ` Pasha Tatashin 2018-09-20 22:29 ` [PATCH v4 3/5] mm: Defer ZONE_DEVICE page initialization to the point where we init pgmap Alexander Duyck 2018-09-20 22:29 ` Alexander Duyck 2018-09-21 19:50 ` Pasha Tatashin 2018-09-21 20:03 ` Alexander Duyck 2018-09-21 20:03 ` Alexander Duyck 2018-09-21 20:14 ` Pasha Tatashin 2018-09-20 22:29 ` [PATCH v4 4/5] async: Add support for queueing on specific node Alexander Duyck 2018-09-20 22:29 ` Alexander Duyck 2018-09-21 14:57 ` Dan Williams 2018-09-21 14:57 ` Dan Williams 2018-09-21 17:02 ` Alexander Duyck 2018-09-21 17:02 ` Alexander Duyck 2018-09-29 8:15 ` [LKP] [async] 06f4f5bfb3: BUG:sleeping_function_called_from_invalid_context_at_include/linux/percpu-rwsem.h kernel test robot 2018-09-29 8:15 ` kernel test robot 2018-09-29 8:15 ` [LKP] " kernel test robot 2018-09-20 22:29 ` [PATCH v4 5/5] nvdimm: Schedule device registration on node local to the device Alexander Duyck 2018-09-20 22:29 ` Alexander Duyck 2018-09-20 22:59 ` Dan Williams 2018-09-20 22:59 ` Dan Williams 2018-09-21 0:16 ` Alexander Duyck 2018-09-21 0:16 ` Alexander Duyck 2018-09-21 0:36 ` Dan Williams 2018-09-21 0:36 ` Dan Williams 2018-09-21 1:33 ` Alexander Duyck 2018-09-21 1:33 ` Alexander Duyck 2018-09-21 2:46 ` Dan Williams 2018-09-21 2:46 ` Dan Williams 2018-09-21 14:46 ` Alexander Duyck 2018-09-21 14:46 ` Alexander Duyck 2018-09-21 14:56 ` Dan Williams 2018-09-21 14:56 ` Dan Williams
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20180920215824.19464.8884.stgit@localhost.localdomain \ --to=alexander.h.duyck@linux.intel.com \ --cc=akpm@linux-foundation.org \ --cc=dave.hansen@intel.com \ --cc=jglisse@redhat.com \ --cc=kirill.shutemov@linux.intel.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=linux-nvdimm@lists.01.org \ --cc=mhocko@suse.com \ --cc=mingo@kernel.org \ --cc=pavel.tatashin@microsoft.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.