linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mikhail Zaslonko <zaslonko@linux.ibm.com>
To: akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	mhocko@kernel.org, Pavel.Tatashin@microsoft.com,
	schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
	gerald.schaefer@de.ibm.com, zaslonko@linux.ibm.com
Subject: [PATCH v2 0/1] Initialize struct pages for the full section
Date: Wed, 12 Dec 2018 18:27:11 +0100	[thread overview]
Message-ID: <20181212172712.34019-1-zaslonko@linux.ibm.com> (raw)

This patch refers to the older thread:
https://marc.info/?t=153658306400001&r=1&w=2

As suggested by Michal Hocko, instead of adjusting memory_hotplug paths,
I have changed memmap_init_zone() to initialize struct pages beyond the
zone end (if zone end is not aligned with the section boundary).

Mikhail Zaslonko (1):
  mm, memory_hotplug: Initialize struct pages for the full memory
    section

 mm/page_alloc.c | 12 ++++++++++++
 1 file changed, 12 insertions(+)

-- 
2.16.4


             reply	other threads:[~2018-12-12 17:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12 17:27 Mikhail Zaslonko [this message]
2018-12-12 17:27 ` [PATCH v2 1/1] mm, memory_hotplug: Initialize struct pages for the full memory section Mikhail Zaslonko
2018-12-13  3:46   ` Wei Yang
     [not found]     ` <e4cebbae-3fcb-f03c-3d0e-a1a44ff0675a@linux.bm.com>
2018-12-13 15:12       ` Wei Yang
     [not found]         ` <674c53e2-e4b3-f21f-4613-b149acef7e53@linux.bm.com>
2018-12-14 10:19           ` Michal Hocko
2018-12-15  0:26             ` Wei Yang
2018-12-13 12:59   ` Michal Hocko
2018-12-14 15:22   ` David Hildenbrand
2018-12-14 15:49     ` David Hildenbrand
2018-12-14 19:23       ` Gerald Schaefer
2018-12-17  9:38         ` David Hildenbrand
2018-12-17 12:28           ` Michal Hocko
2018-12-17 13:29             ` David Hildenbrand
2018-12-17 13:35               ` 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=20181212172712.34019-1-zaslonko@linux.ibm.com \
    --to=zaslonko@linux.ibm.com \
    --cc=Pavel.Tatashin@microsoft.com \
    --cc=akpm@linux-foundation.org \
    --cc=gerald.schaefer@de.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=schwidefsky@de.ibm.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 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).