Re: [PATCH V3 1/2] mm: hotplug: implement non-movable version of get_user_pages() called get_user_pages_non_movable()

Hi Yasuaki, On 03/06/2013 03:48 PM, Yasuaki Ishimatsu wrote: > Hi Lin, > > IMHO, current implementation depends on luck. So even if system has > many non movable memory, get_user_pages_non_movable() may not allocate > non movable memory. Sorry, I'm not quite understand here, since the to be pinn

Re: [PATCH V3 1/2] mm: hotplug: implement non-movable version of get_user_pages() called get_user_pages_non_movable()

Hi Lin, IMHO, current implementation depends on luck. So even if system has many non movable memory, get_user_pages_non_movable() may not allocate non movable memory. At following thread, Marek Szyprowski implemented similar feature which allocates non movable memory by "get_user_pages()". http

Re: [PATCH V3 1/2] mm: hotplug: implement non-movable version of get_user_pages() called get_user_pages_non_movable()

Hi Andrew, Mel and other guys, How about this V3 patch, any comments? thanks, linfeng On 02/21/2013 07:01 PM, Lin Feng wrote: > get_user_pages() always tries to allocate pages from movable zone, which is > not > reliable to memory hotremove framework in some case. > > This patch introduces a

[PATCH V3 1/2] mm: hotplug: implement non-movable version of get_user_pages() called get_user_pages_non_movable()

get_user_pages() always tries to allocate pages from movable zone, which is not reliable to memory hotremove framework in some case. This patch introduces a new library function called get_user_pages_non_movable() to pin pages only from zone non-movable in memory. It's a wrapper of get_user_page