From: Alexander Duyck <alexander.duyck@gmail.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: alexander.h.duyck@intel.com, pavel.tatashin@microsoft.com,
mhocko@suse.com, akpm@linux-foundation.org, mingo@kernel.org,
kirill.shutemov@linux.intel.com
Subject: [PATCH 0/2] Address issues slowing memory init
Date: Tue, 04 Sep 2018 11:33:32 -0700 [thread overview]
Message-ID: <20180904181550.4416.50701.stgit@localhost.localdomain> (raw)
This patch series is meant to address some issues I consider to be
low-hanging fruit in regards to memory initialization optimization.
With these two changes I am able to cut the hot-plug memory initialization
times in my environment in half.
---
Alexander Duyck (2):
mm: Move page struct poisoning from CONFIG_DEBUG_VM to CONFIG_DEBUG_VM_PGFLAGS
mm: Create non-atomic version of SetPageReserved for init use
include/linux/page-flags.h | 1 +
mm/memblock.c | 2 +-
mm/page_alloc.c | 4 ++--
mm/sparse.c | 2 +-
4 files changed, 5 insertions(+), 4 deletions(-)
--
next reply other threads:[~2018-09-04 18:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 18:33 Alexander Duyck [this message]
2018-09-04 18:33 ` [PATCH 1/2] mm: Move page struct poisoning from CONFIG_DEBUG_VM to CONFIG_DEBUG_VM_PGFLAGS Alexander Duyck
2018-09-04 19:25 ` Dave Hansen
2018-09-04 19:54 ` Alexander Duyck
2018-09-04 20:07 ` Pasha Tatashin
2018-09-04 21:13 ` Alexander Duyck
2018-09-04 21:44 ` Pasha Tatashin
2018-09-05 6:10 ` Michal Hocko
2018-09-05 15:32 ` Alexander Duyck
2018-09-06 5:38 ` Michal Hocko
2018-09-04 18:33 ` [PATCH 2/2] mm: Create non-atomic version of SetPageReserved for init use Alexander Duyck
2018-09-04 19:27 ` Dave Hansen
2018-09-05 6:24 ` Michal Hocko
2018-09-05 20:18 ` Alexander Duyck
2018-09-05 20:22 ` Pasha Tatashin
2018-09-05 20:35 ` Alexander Duyck
2018-09-06 5:41 ` Michal Hocko
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=20180904181550.4416.50701.stgit@localhost.localdomain \
--to=alexander.duyck@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.h.duyck@intel.com \
--cc=kirill.shutemov@linux.intel.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 \
/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 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.