linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mel@csn.ul.ie>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Ingo Korb <ingo@akana.de>,
	linux-mm@kvack.org, akpm@linux-foundation.org,
	cl@linux-foundation.org, yinghai@kernel.org,
	andi.kleen@intel.com, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: __offline_isolated_pages may offline too many pages
Date: Thu, 16 Dec 2010 10:26:41 +0000	[thread overview]
Message-ID: <20101216102641.GK13914@csn.ul.ie> (raw)
In-Reply-To: <20101216090657.9d3aaa4c.kamezawa.hiroyu@jp.fujitsu.com>

On Thu, Dec 16, 2010 at 09:06:57AM +0900, KAMEZAWA Hiroyuki wrote:
> On Wed, 15 Dec 2010 10:25:51 +0100
> Ingo Korb <ingo@akana.de> wrote:
> 
> > On 15.12.2010 01:21, KAMEZAWA Hiroyuki wrote:
> > 
> > > It's designed for offline memory section>  MAX_ORDER. pageblock_nr_pages
> > > is tend to be smaller than that.
> > >
> > > Do you see the problem with _exsisting_ user interface of memory hotplug ?
> > > I think we have no control other than memory section.
> > 
> > The existing, exported interface (remove_memory() - the check itself is 
> > in offline_pages()) only checks if both start and end of the 
> > to-be-removed block are aligned to pageblock_nr_pages. As you noted the 
> > actual size and alignment requirements in __offline_isolated_pages can 
> > be larger that that, so I think the checks in offline_pages() should be 
> > changed (if 1<<MAX_ORDER is always >= pageblock_nr_pages) or extended 
> > (if there can be any relation between the two).
> > 
> 
> Ok, maybe my mistake. This is a fix. Thank you for reporting.
> ==
> 
> offline_pages()'s sanity check of given range is wrong. It should
> be aligned to MAX_ORDER. Current exsiting caller uses SECTION_SIZE
> alignment, so this change has no influence to exsisting callers.
> 
> Reported-by: Ingo Korb <ingo@akana.de>
> Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>

Other than the spelling mistakes in the changelog and the lack of a
subject;

Acked-by: Mel Gorman <mel@csn.ul.ie>

> ---
>  mm/memory_hotplug.c |   10 +++++++---
>  1 file changed, 7 insertions(+), 3 deletions(-)
> 
> Index: linux-2.6.37-rc5/mm/memory_hotplug.c
> ===================================================================
> --- linux-2.6.37-rc5.orig/mm/memory_hotplug.c
> +++ linux-2.6.37-rc5/mm/memory_hotplug.c
> @@ -798,10 +798,14 @@ static int offline_pages(unsigned long s
>  	struct memory_notify arg;
>  
>  	BUG_ON(start_pfn >= end_pfn);
> -	/* at least, alignment against pageblock is necessary */
> -	if (!IS_ALIGNED(start_pfn, pageblock_nr_pages))
> +	/*
> +	 * Considering buddy allocator which joins nearby pages, the range
> +	 * in offline should be aligned to MAX_ORDER. If not, isolated
> +	 * page will be joined to other (not isolated) pages.
> +	 */
> +	if (!IS_ALIGNED(start_pfn, MAX_ORDER_NR_PAGES))
>  		return -EINVAL;
> -	if (!IS_ALIGNED(end_pfn, pageblock_nr_pages))
> +	if (!IS_ALIGNED(end_pfn, MAX_ORDER_NR_PAGES))
>  		return -EINVAL;
>  	/* This makes hotplug much easier...and readable.
>  	   we assume this for now. .*/
> 

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

--
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 policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-12-16 10:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14 15:01 PROBLEM: __offline_isolated_pages may offline too many pages Ingo Korb
2010-12-15  0:21 ` KAMEZAWA Hiroyuki
2010-12-15  9:25   ` Ingo Korb
2010-12-16  0:06     ` KAMEZAWA Hiroyuki
2010-12-16 10:26       ` Mel Gorman [this message]
2010-12-16 23:57         ` [PATCH] memory hotplug: fix alignment check (Was " KAMEZAWA Hiroyuki

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=20101216102641.GK13914@csn.ul.ie \
    --to=mel@csn.ul.ie \
    --cc=akpm@linux-foundation.org \
    --cc=andi.kleen@intel.com \
    --cc=cl@linux-foundation.org \
    --cc=ingo@akana.de \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=yinghai@kernel.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).