Hi Wu,
Sorry for such a long delay.
On 11/26/2012 08:40 PM, wujianguo wrote:
Hi Tang,
I tested this patchset in x86_64, and I found that this patch didn't
work as expected.
For example, if node2's memory pfn range is [0x68-0x98),
I boot kernel with movablecore_map=4G@0x6
On 12/07/2012 01:41 AM, H. Peter Anvin wrote:
> On 12/06/2012 09:28 AM, Jiang Liu wrote:
>> Hi hpa and Tang,
>> How do you think about the attached patches, which reserves memory
>> for hotplug from memblock/bootmem allocator at early booting stages?
>
> I don't see any attached patches?
>
>
On 12/06/2012 09:28 AM, Jiang Liu wrote:
> Hi hpa and Tang,
> How do you think about the attached patches, which reserves memory
> for hotplug from memblock/bootmem allocator at early booting stages?
I don't see any attached patches?
-hpa
--
To unsubscribe from this list: send the
Hi hpa and Tang,
How do you think about the attached patches, which reserves memory
for hotplug from memblock/bootmem allocator at early booting stages?
Logically we split the task into three parts:
1) Provide a mechanism to specify zone_movable[] by kernel parameter.
Patch 1-4 f
On 11/26/2012 07:15 PM, Wen Congyang wrote:
Hi, hpa
The problem is that:
node1 address rang: [18G, 34G), and the user specifies movable map is [8G, 24G).
We don't know node1's address range before numa init. So we can't prevent
allocating boot memory in the range [24G, 34G).
The movable memory
At 11/26/2012 11:48 PM, H. Peter Anvin Wrote:
> On 11/26/2012 05:15 AM, Tang Chen wrote:
>>
>> Hi Wu,
>>
>> That is really a problem. And, before numa memory got initialized,
>> memblock subsystem would be used to allocate memory. I didn't find any
>> approach that could fully address it when I mak
At 11/27/2012 11:22 AM, Jianguo Wu Wrote:
> On 2012/11/27 11:19, Wen Congyang wrote:
>
>> At 11/27/2012 08:58 AM, Jianguo Wu Wrote:
>>> On 2012/11/26 23:48, H. Peter Anvin wrote:
>>>
On 11/26/2012 05:15 AM, Tang Chen wrote:
>
> Hi Wu,
>
> That is really a problem. And, before
On 2012/11/27 11:19, Wen Congyang wrote:
> At 11/27/2012 08:58 AM, Jianguo Wu Wrote:
>> On 2012/11/26 23:48, H. Peter Anvin wrote:
>>
>>> On 11/26/2012 05:15 AM, Tang Chen wrote:
Hi Wu,
That is really a problem. And, before numa memory got initialized,
memblock subsystem w
At 11/27/2012 08:58 AM, Jianguo Wu Wrote:
> On 2012/11/26 23:48, H. Peter Anvin wrote:
>
>> On 11/26/2012 05:15 AM, Tang Chen wrote:
>>>
>>> Hi Wu,
>>>
>>> That is really a problem. And, before numa memory got initialized,
>>> memblock subsystem would be used to allocate memory. I didn't find any
On 11/26/2012 05:12 PM, Jiang Liu wrote:
Hi Peter,
I have tried to reserved movable memory from bootmem allocator, but the
ACPICA subsystem is initialized later than setting up movable zone.
So still trying to figure out a way to setup/reserve movable zones
according to information from static A
On 2012-11-26 23:48, H. Peter Anvin wrote:
> On 11/26/2012 05:15 AM, Tang Chen wrote:
>>
>> Hi Wu,
>>
>> That is really a problem. And, before numa memory got initialized,
>> memblock subsystem would be used to allocate memory. I didn't find any
>> approach that could fully address it when I making
On 2012/11/26 23:48, H. Peter Anvin wrote:
> On 11/26/2012 05:15 AM, Tang Chen wrote:
>>
>> Hi Wu,
>>
>> That is really a problem. And, before numa memory got initialized,
>> memblock subsystem would be used to allocate memory. I didn't find any
>> approach that could fully address it when I makin
On 11/26/2012 05:15 AM, Tang Chen wrote:
>
> Hi Wu,
>
> That is really a problem. And, before numa memory got initialized,
> memblock subsystem would be used to allocate memory. I didn't find any
> approach that could fully address it when I making the patches. There
> always be risk that membloc
On 11/26/2012 08:40 PM, wujianguo wrote:
Hi Tang,
I tested this patchset in x86_64, and I found that this patch didn't
work as expected.
For example, if node2's memory pfn range is [0x68-0x98),
I boot kernel with movablecore_map=4G@0x68000, all memory in node2 will be
On 11/26/2012 08:22 PM, wujianguo wrote:
On 2012-11-23 18:44, Tang Chen wrote:
This patch make sure bootmem will not allocate memory from areas that
may be ZONE_MOVABLE. The map info is from movablecore_map boot option.
Signed-off-by: Tang Chen
Signed-off-by: Lai Jiangshan
Reviewed-by: Wen Cong
Hi Tang,
I tested this patchset in x86_64, and I found that this patch didn't
work as expected.
For example, if node2's memory pfn range is [0x68-0x98),
I boot kernel with movablecore_map=4G@0x68000, all memory in node2 will be
in ZONE_MOVABLE, but bootmem still can be a
On 2012-11-23 18:44, Tang Chen wrote:
> This patch make sure bootmem will not allocate memory from areas that
> may be ZONE_MOVABLE. The map info is from movablecore_map boot option.
>
> Signed-off-by: Tang Chen
> Signed-off-by: Lai Jiangshan
> Reviewed-by: Wen Congyang
> Tested-by: Lin Feng
>
This patch make sure bootmem will not allocate memory from areas that
may be ZONE_MOVABLE. The map info is from movablecore_map boot option.
Signed-off-by: Tang Chen
Signed-off-by: Lai Jiangshan
Reviewed-by: Wen Congyang
Tested-by: Lin Feng
---
include/linux/memblock.h |1 +
mm/memblock.c
18 matches
Mail list logo
