linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lin Feng <linfeng@cn.fujitsu.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: akpm@linux-foundation.org, kamezawa.hiroyu@jp.fujitsu.com,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] memory-hotplug: mm/Kconfig: move auto selects from MEMORY_HOTPLUG to MEMORY_HOTREMOVE as needed
Date: Mon, 21 Jan 2013 09:50:19 +0800	[thread overview]
Message-ID: <50FC9EDB.7060105@cn.fujitsu.com> (raw)
In-Reply-To: <20130118135828.GD10701@dhcp22.suse.cz>

Hi Michal,

On 01/18/2013 09:58 PM, Michal Hocko wrote:
> On Fri 18-01-13 15:54:36, Lin Feng wrote:
>> Besides page_isolation.c selected by MEMORY_ISOLATION under MEMORY_HOTPLUG
>> is also such case, move it too.
> 
> Yes, it seems that only HOTREMOVE needs MEMORY_ISOLATION but that should
> be done in a separate patch as this change is already upstream and
> should be merged separately. It would also be nice to mention which
I didn't notice such rules before, I will take care next time :)

> functions are we talking about. AFAICS:
> alloc_migrate_target, test_pages_isolated, start_isolate_page_range and
> undo_isolate_page_range.
> 
Anyway, thanks all your good suggestions for the fixes in this series.

thanks again,
linfeng 

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2013-01-21  1:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18  7:54 Lin Feng
2013-01-18 13:58 ` Michal Hocko
2013-01-21  1:50   ` Lin Feng [this message]
2013-02-21 21:18 ` [patch -mm] memory-hotplug: implement register_page_bootmem_info_section of sparse-vmemmap fix fix fix fix fix 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=50FC9EDB.7060105@cn.fujitsu.com \
    --to=linfeng@cn.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    /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