Hi Changsheng,
Thank you for your comments.
I'm on vacation. So After that, I'll repost the patch.
Thanks,
Yasuaki Ishimatsu
On Sun, 6 Sep 2015 16:33:42 +0800
Changsheng Liu wrote:
>
>
> On 9/1/2015 23:37, Yasuaki Ishimatsu wrote:
> > On Mon, 31 Aug 2015 01:58:40 -0400
> > Changsheng Liu
Hi Changsheng,
Thank you for your comments.
I'm on vacation. So After that, I'll repost the patch.
Thanks,
Yasuaki Ishimatsu
On Sun, 6 Sep 2015 16:33:42 +0800
Changsheng Liu wrote:
>
>
> On 9/1/2015 23:37, Yasuaki Ishimatsu wrote:
> > On Mon, 31 Aug 2015 01:58:40
On 9/1/2015 23:37, Yasuaki Ishimatsu wrote:
On Mon, 31 Aug 2015 01:58:40 -0400
Changsheng Liu wrote:
From: Changsheng Liu
After the user config CONFIG_MOVABLE_NODE and movable_node kernel option,
When the memory is hot added, should_add_memory_movable() return 0
because all zones
On 9/1/2015 23:37, Yasuaki Ishimatsu wrote:
On Mon, 31 Aug 2015 01:58:40 -0400
Changsheng Liu wrote:
From: Changsheng Liu
After the user config CONFIG_MOVABLE_NODE and movable_node kernel option,
When the memory is hot added,
On 9/1/2015 23:37, Yasuaki Ishimatsu wrote:
On Mon, 31 Aug 2015 01:58:40 -0400
Changsheng Liu wrote:
From: Changsheng Liu
After the user config CONFIG_MOVABLE_NODE and movable_node kernel option,
When the memory is hot added, should_add_memory_movable() return 0
because all zones
On 9/1/2015 23:37, Yasuaki Ishimatsu wrote:
On Mon, 31 Aug 2015 01:58:40 -0400
Changsheng Liu wrote:
From: Changsheng Liu
After the user config CONFIG_MOVABLE_NODE and movable_node kernel option,
When the memory is hot added,
On Mon, 31 Aug 2015 01:58:40 -0400
Changsheng Liu wrote:
> From: Changsheng Liu
>
> After the user config CONFIG_MOVABLE_NODE and movable_node kernel option,
> When the memory is hot added, should_add_memory_movable() return 0
> because all zones including movable zone are empty,
> so the
On 8/31/2015 21:08, Vlastimil Babka wrote:
On 08/31/2015 07:58 AM, Changsheng Liu wrote:
From: Changsheng Liu
After the user config CONFIG_MOVABLE_NODE and movable_node kernel
option,
When the memory is hot added, should_add_memory_movable() return 0
because all zones including movable
On 8/31/2015 21:08, Vlastimil Babka wrote:
On 08/31/2015 07:58 AM, Changsheng Liu wrote:
From: Changsheng Liu
After the user config CONFIG_MOVABLE_NODE and movable_node kernel
option,
When the memory is hot added, should_add_memory_movable() return 0
because all
On Mon, 31 Aug 2015 01:58:40 -0400
Changsheng Liu wrote:
> From: Changsheng Liu
>
> After the user config CONFIG_MOVABLE_NODE and movable_node kernel option,
> When the memory is hot added, should_add_memory_movable() return 0
> because all
On 08/31/2015 07:58 AM, Changsheng Liu wrote:
From: Changsheng Liu
After the user config CONFIG_MOVABLE_NODE and movable_node kernel option,
When the memory is hot added, should_add_memory_movable() return 0
because all zones including movable zone are empty,
so the memory that was hot added
On 08/31/2015 07:58 AM, Changsheng Liu wrote:
From: Changsheng Liu
After the user config CONFIG_MOVABLE_NODE and movable_node kernel option,
When the memory is hot added, should_add_memory_movable() return 0
because all zones including movable zone are empty,
so the
12 matches
Mail list logo