From: Alexander Duyck <alexander.h.duyck@linux.intel.com>
To: sparclinux@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Cc: pavel.tatashin@microsoft.com, mhocko@suse.com,
dave.jiang@intel.com, alexander.h.duyck@linux.intel.com,
dan.j.williams@intel.com, willy@infradead.org, mingo@kernel.org,
khalid.aziz@oracle.com, rppt@linux.vnet.ibm.com, vbabka@suse.cz,
akpm@linux-foundation.org, ldufour@linux.vnet.ibm.com,
davem@davemloft.net, kirill.shutemov@linux.intel.com
Subject: [RFC mm PATCH 0/5] mm: Deferred page init improvements
Date: Wed, 26 Sep 2018 16:28:20 -0700 [thread overview]
Message-ID: <20180926232117.17365.72207.stgit@localhost.localdomain> (raw)
This patchset is essentially a refactor of the page initialization logic
to provide for better code reuse while providing a significant improvement
in deferred page initialization performance.
In my testing I have seen a 3:1 reduction in the time needed for deferred
memory initialization on two different x86_64 based test systems I have.
In addition this provides a very slight improvement for the hotplug memory
initialization, although the improvement doesn't exceed 5% from what I can
tell and that is to be expected since most of the changes related to
hotplug initialization are just code clean-up to allow for reuse. I had
been considering using a large memset for the entire pageblock I was
initializing which showed a significant speedup for persistent memory init
however that showed no improvements to a slight regression for regular
deferred initialization of standard memory.
---
Alexander Duyck (5):
mm: Use mm_zero_struct_page from SPARC on all 64b architectures
mm: Drop meminit_pfn_in_nid as it is redundant
mm: Use memblock/zone specific iterator for handling deferred page init
mm: Move hot-plug specific memory init into separate functions and optimize
mm: Use common iterator for deferred_init_pages and deferred_free_pages
arch/sparc/include/asm/pgtable_64.h | 30 --
include/linux/memblock.h | 58 ++++
include/linux/mm.h | 33 ++
mm/memblock.c | 63 ++++
mm/page_alloc.c | 555 +++++++++++++++++++++--------------
5 files changed, 485 insertions(+), 254 deletions(-)
--
next reply other threads:[~2018-09-26 23:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 23:28 Alexander Duyck [this message]
2018-09-26 23:28 ` [RFC mm PATCH 1/5] mm: Use mm_zero_struct_page from SPARC on all 64b architectures Alexander Duyck
2018-09-26 23:28 ` [RFC mm PATCH 2/5] mm: Drop meminit_pfn_in_nid as it is redundant Alexander Duyck
2018-09-26 23:28 ` [RFC mm PATCH 3/5] mm: Use memblock/zone specific iterator for handling deferred page init Alexander Duyck
2018-09-26 23:28 ` [RFC mm PATCH 4/5] mm: Move hot-plug specific memory init into separate functions and optimize Alexander Duyck
2018-09-26 23:28 ` [RFC mm PATCH 5/5] mm: Use common iterator for deferred_init_pages and deferred_free_pages Alexander Duyck
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=20180926232117.17365.72207.stgit@localhost.localdomain \
--to=alexander.h.duyck@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=davem@davemloft.net \
--cc=khalid.aziz@oracle.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=ldufour@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=pavel.tatashin@microsoft.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=sparclinux@vger.kernel.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).