From: Greg KH <greg@kroah.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mel Gorman <mgorman@suse.de>, linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
nfont@linux.vnet.ibm.com,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [PATCH] mm: memory hotplug: Check if pages are correctly reserved on a per-section basis
Date: Mon, 10 Oct 2011 16:35:31 -0700 [thread overview]
Message-ID: <20111010233531.GA7234@kroah.com> (raw)
In-Reply-To: <20111010162813.7a470ae4.akpm@linux-foundation.org>
On Mon, Oct 10, 2011 at 04:28:13PM -0700, Andrew Morton wrote:
> On Mon, 10 Oct 2011 16:24:03 -0700
> Greg KH <greg@kroah.com> wrote:
>
> > On Mon, Oct 10, 2011 at 03:00:38PM -0700, Andrew Morton wrote:
> > > On Mon, 10 Oct 2011 08:11:19 +0100
> > > Mel Gorman <mgorman@suse.de> wrote:
> > >
> > > > It is expected that memory being brought online is PageReserved
> > > > similar to what happens when the page allocator is being brought up.
> > > > Memory is onlined in "memory blocks" which consist of one or more
> > > > sections. Unfortunately, the code that verifies PageReserved is
> > > > currently assuming that the memmap backing all these pages is virtually
> > > > contiguous which is only the case when CONFIG_SPARSEMEM_VMEMMAP is set.
> > > > As a result, memory hot-add is failing on !VMEMMAP configurations
> > > > with the message;
> > > >
> > > > kernel: section number XXX page number 256 not reserved, was it already online?
> > > >
> > > > This patch updates the PageReserved check to lookup struct page once
> > > > per section to guarantee the correct struct page is being checked.
> > > >
> > >
> > > Nathan's earlier version of this patch is already in linux-next, via
> > > Greg. We should drop the old version and get the new one merged
> > > instead.
> >
> > Ok, care to send me what exactly needs to be reverted and what needs to
> > be added?
>
> Drop
>
> commit 54f23eb7ba7619de85d8edca6e5336bc33072dbd
> Author: Nathan Fontenot <nfont@austin.ibm.com>
> Date: Mon Sep 26 10:22:33 2011 -0500
>
> memory hotplug: Correct page reservation checking
>
> and replace it with start-of-this-thread.
>
> That's assuming that Mel's update passes Nathan's review and testing :)
Ok, I'll wait for that review and testing, and then can someone send me
the patch at the start-of-this-thread as I no longer seem to be able to
find it :(
greg k-h
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-10-10 23:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 7:11 [PATCH] mm: memory hotplug: Check if pages are correctly reserved on a per-section basis Mel Gorman
2011-10-10 22:00 ` Andrew Morton
2011-10-10 23:24 ` Greg KH
2011-10-10 23:28 ` Andrew Morton
2011-10-10 23:35 ` Greg KH [this message]
2011-10-10 23:41 ` Andrew Morton
2011-10-11 4:26 ` David Rientjes
2011-10-11 7:27 ` Mel Gorman
2011-10-11 14:44 ` Nathan Fontenot
2011-10-12 1:16 ` IBM
2011-10-17 14:38 ` Mel Gorman
2011-10-18 0:45 ` KAMEZAWA Hiroyuki
2011-10-20 5:19 ` David Rientjes
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=20111010233531.GA7234@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=nfont@linux.vnet.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).