Hello, Xishi, Tang.
On Mon, Aug 18, 2014 at 11:18:00AM +0800, Xishi Qiu wrote:
> If all the nodes are marked hotpluggable flag, alloc node data will fail.
> Because __next_mem_range_rev() will skip the hotpluggable memory regions.
> numa_register_memblks()
> setup_node_data()
>
Hello, Xishi, Tang.
On Mon, Aug 18, 2014 at 11:18:00AM +0800, Xishi Qiu wrote:
If all the nodes are marked hotpluggable flag, alloc node data will fail.
Because __next_mem_range_rev() will skip the hotpluggable memory regions.
numa_register_memblks()
setup_node_data()
On 2014/8/18 9:13, tangchen wrote:
> Hi tj,
>
> On 08/17/2014 07:08 PM, Tejun Heo wrote:
>> Hello,
>>
>> On Sat, Aug 16, 2014 at 10:36:41PM +0800, Xishi Qiu wrote:
>>> numa_clear_node_hotplug()? There is only numa_clear_kernel_node_hotplug().
>> Yeah, that one.
>>
>>> If we don't clear
On 2014/8/17 19:08, Tejun Heo wrote:
> Hello,
>
> On Sat, Aug 16, 2014 at 10:36:41PM +0800, Xishi Qiu wrote:
>> numa_clear_node_hotplug()? There is only numa_clear_kernel_node_hotplug().
>
> Yeah, that one.
>
>> If we don't clear hotpluggable flag in free_low_memory_core_early(), the
>>
Hi tj,
On 08/17/2014 07:08 PM, Tejun Heo wrote:
Hello,
On Sat, Aug 16, 2014 at 10:36:41PM +0800, Xishi Qiu wrote:
numa_clear_node_hotplug()? There is only numa_clear_kernel_node_hotplug().
Yeah, that one.
If we don't clear hotpluggable flag in free_low_memory_core_early(), the
memory which
Hello,
On Sat, Aug 16, 2014 at 10:36:41PM +0800, Xishi Qiu wrote:
> numa_clear_node_hotplug()? There is only numa_clear_kernel_node_hotplug().
Yeah, that one.
> If we don't clear hotpluggable flag in free_low_memory_core_early(), the
> memory which marked hotpluggable flag will not free to
Hello,
On Sat, Aug 16, 2014 at 10:36:41PM +0800, Xishi Qiu wrote:
numa_clear_node_hotplug()? There is only numa_clear_kernel_node_hotplug().
Yeah, that one.
If we don't clear hotpluggable flag in free_low_memory_core_early(), the
memory which marked hotpluggable flag will not free to buddy
Hi tj,
On 08/17/2014 07:08 PM, Tejun Heo wrote:
Hello,
On Sat, Aug 16, 2014 at 10:36:41PM +0800, Xishi Qiu wrote:
numa_clear_node_hotplug()? There is only numa_clear_kernel_node_hotplug().
Yeah, that one.
If we don't clear hotpluggable flag in free_low_memory_core_early(), the
memory which
On 2014/8/17 19:08, Tejun Heo wrote:
Hello,
On Sat, Aug 16, 2014 at 10:36:41PM +0800, Xishi Qiu wrote:
numa_clear_node_hotplug()? There is only numa_clear_kernel_node_hotplug().
Yeah, that one.
If we don't clear hotpluggable flag in free_low_memory_core_early(), the
memory which
On 2014/8/18 9:13, tangchen wrote:
Hi tj,
On 08/17/2014 07:08 PM, Tejun Heo wrote:
Hello,
On Sat, Aug 16, 2014 at 10:36:41PM +0800, Xishi Qiu wrote:
numa_clear_node_hotplug()? There is only numa_clear_kernel_node_hotplug().
Yeah, that one.
If we don't clear hotpluggable flag in
On 2014/8/16 21:04, Tejun Heo wrote:
> On Mon, Aug 11, 2014 at 09:31:22PM +0800, Xishi Qiu wrote:
>> Let memblock skip the hotpluggable memory regions in __next_mem_range(),
>> it is used to to prevent memblock from allocating hotpluggable memory
>> for the kernel at early time. The code is the
On Mon, Aug 11, 2014 at 09:31:22PM +0800, Xishi Qiu wrote:
> Let memblock skip the hotpluggable memory regions in __next_mem_range(),
> it is used to to prevent memblock from allocating hotpluggable memory
> for the kernel at early time. The code is the same as __next_mem_range_rev().
>
> Clear
On Mon, Aug 11, 2014 at 09:31:22PM +0800, Xishi Qiu wrote:
Let memblock skip the hotpluggable memory regions in __next_mem_range(),
it is used to to prevent memblock from allocating hotpluggable memory
for the kernel at early time. The code is the same as __next_mem_range_rev().
Clear
On 2014/8/16 21:04, Tejun Heo wrote:
On Mon, Aug 11, 2014 at 09:31:22PM +0800, Xishi Qiu wrote:
Let memblock skip the hotpluggable memory regions in __next_mem_range(),
it is used to to prevent memblock from allocating hotpluggable memory
for the kernel at early time. The code is the same as
Let memblock skip the hotpluggable memory regions in __next_mem_range(),
it is used to to prevent memblock from allocating hotpluggable memory
for the kernel at early time. The code is the same as __next_mem_range_rev().
Clear hotpluggable flag before releasing free pages to the buddy allocator.
Let memblock skip the hotpluggable memory regions in __next_mem_range(),
it is used to to prevent memblock from allocating hotpluggable memory
for the kernel at early time. The code is the same as __next_mem_range_rev().
Clear hotpluggable flag before releasing free pages to the buddy allocator.
16 matches
Mail list logo
