Hi Srivatsa,
I applied this patchset, and run genload(from LTP) test: numactl --membind=1
./genload -m 100,
then got a "general protection fault", and system was going to reboot.
If I revert [RFC PATCH 7/8], and run this test again, genload will be killed
due to OOM,
but the system is OK, no
Hi Srivatsa,
I got following compile waring:
WARNING: vmlinux.o(.text+0x10b320): Section mismatch in reference from the
function init_zone_memory_regions() to the function
.meminit.text:__absent_pages_in_range()
The function init_zone_memory_regions() references
the function __meminit
Hi Srivatsa,
I got following compile waring:
WARNING: vmlinux.o(.text+0x10b320): Section mismatch in reference from the
function init_zone_memory_regions() to the function
.meminit.text:__absent_pages_in_range()
The function init_zone_memory_regions() references
the function __meminit
Hi Srivatsa,
I applied this patchset, and run genload(from LTP) test: numactl --membind=1
./genload -m 100,
then got a general protection fault, and system was going to reboot.
If I revert [RFC PATCH 7/8], and run this test again, genload will be killed
due to OOM,
but the system is OK, no
On 2012-11-23 18:44, Tang Chen wrote:
> [What we are doing]
> This patchset provide a boot option for user to specify ZONE_MOVABLE memory
> map for each node in the system.
>
> movablecore_map=nn[KMG]@ss[KMG]
>
Hi Tang,
DMA address can't be set as movable, if some one boot kernel with
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
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
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 tangc...@cn.fujitsu.com
Signed-off-by: Lai Jiangshan la...@cn.fujitsu.com
Reviewed-by:
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
On 2012-11-23 18:44, Tang Chen wrote:
[What we are doing]
This patchset provide a boot option for user to specify ZONE_MOVABLE memory
map for each node in the system.
movablecore_map=nn[KMG]@ss[KMG]
Hi Tang,
DMA address can't be set as movable, if some one boot kernel with
On 2012-10-22 15:11, Wen Congyang wrote:
> Hi, Wu
>
> Sorry for late reply.
>
> At 10/09/2012 04:26 PM, wujianguo Wrote:
>> Hi Congyang,
>> I think we should also free pages which are used by page tables after
>> removing
>> page tables of the memory
On 2012-10-22 15:11, Wen Congyang wrote:
Hi, Wu
Sorry for late reply.
At 10/09/2012 04:26 PM, wujianguo Wrote:
Hi Congyang,
I think we should also free pages which are used by page tables after
removing
page tables of the memory.
It is OK to do it.
From: Jianguo Wu wujian
Hi Congyang,
I think we should also free pages which are used by page tables after
removing
page tables of the memory.
From: Jianguo Wu
Signed-off-by: Jianguo Wu
Signed-off-by: Jiang Liu
---
arch/x86/mm/init_64.c | 110 +++-
1 files
Hi Congyang,
I think we should also free pages which are used by page tables after
removing
page tables of the memory.
From: Jianguo Wu wujian...@huawei.com
Signed-off-by: Jianguo Wu wujian...@huawei.com
Signed-off-by: Jiang Liu jiang@huawei.com
---
arch/x86/mm/init_64.c | 110
From: Jianguo Wu
In arch ia64, has following definition:
extern u8 numa_slit[MAX_NUMNODES * MAX_NUMNODES];
#define node_distance(from,to) (numa_slit[(from) * num_online_nodes() + (to)])
num_online_nodes() is a variable value, it can be changed after hot-remove/add
a node.
I my practice, I
On 2012-8-3 15:49, we...@cn.fujitsu.com wrote:
> From: Yasuaki Ishimatsu
>
> When calling remove_memory_block(), the function shows following message at
> device_release().
>
> Device 'memory528' does not have a release() function, it is broken and must
> be fixed.
>
I found this warning too
On 2012-8-3 15:49, we...@cn.fujitsu.com wrote:
From: Yasuaki Ishimatsu isimatu.yasu...@jp.fujitsu.com
When calling remove_memory_block(), the function shows following message at
device_release().
Device 'memory528' does not have a release() function, it is broken and must
be fixed.
I
From: Jianguo Wu wujian...@huawei.com
In arch ia64, has following definition:
extern u8 numa_slit[MAX_NUMNODES * MAX_NUMNODES];
#define node_distance(from,to) (numa_slit[(from) * num_online_nodes() + (to)])
num_online_nodes() is a variable value, it can be changed after hot-remove/add
a node.
I
From: Jianguo Wu
I found following definition in include/linux/memory.h, in my IA64
platform, SECTION_SIZE_BITS is equal to 32, and MIN_MEMORY_BLOCK_SIZE will be 0.
#define MIN_MEMORY_BLOCK_SIZE (1 << SECTION_SIZE_BITS)
Because MIN_MEMORY_BLOCK_SIZE is int type and length of 32bits,
so
Hi Michal,
Thanks for your comments and review.
On 2012-8-23 23:48, Michal Hocko wrote:
> [Fixed gregkh email address]
>
> On Tue 21-08-12 11:46:10, wujianguo wrote:
>> From: Jianguo Wu
>>
>> Hi all,
>> I found following definition in include/linux
On 2012-8-21 11:55, Petr Tesarik wrote:
> Dne Po 20. srpna 2012 08:38:10 wujianguo napsal(a):
>> From: Jianguo Wu
>>
>> Hi all,
>> I think zone->present_pages indicates pages that buddy system can
>> management, it should be:
>> zone->
On 2012-8-21 11:55, Petr Tesarik wrote:
Dne Po 20. srpna 2012 08:38:10 wujianguo napsal(a):
From: Jianguo Wu wujian...@huawei.com
Hi all,
I think zone-present_pages indicates pages that buddy system can
management, it should be:
zone-present_pages = spanned pages - absent pages
Hi Michal,
Thanks for your comments and review.
On 2012-8-23 23:48, Michal Hocko wrote:
[Fixed gregkh email address]
On Tue 21-08-12 11:46:10, wujianguo wrote:
From: Jianguo Wu wujian...@huawei.com
Hi all,
I found following definition in include/linux/memory.h, in my IA64
From: Jianguo Wu wujian...@huawei.com
I found following definition in include/linux/memory.h, in my IA64
platform, SECTION_SIZE_BITS is equal to 32, and MIN_MEMORY_BLOCK_SIZE will be 0.
#define MIN_MEMORY_BLOCK_SIZE (1 SECTION_SIZE_BITS)
Because MIN_MEMORY_BLOCK_SIZE is int type and length
From: Jianguo Wu
Hi all,
I found following definition in include/linux/memory.h, in my IA64
platform, SECTION_SIZE_BITS is equal to 32, and MIN_MEMORY_BLOCK_SIZE will be 0.
#define MIN_MEMORY_BLOCK_SIZE (1 << SECTION_SIZE_BITS)
Because MIN_MEMORY_BLOCK_SIZE is
From: Jianguo Wu
Hi all,
When doing memory-hot-plug, We found node distance is wrong after
offline
a node in IA64 platform. For example system has 4 nodes:
node distances:
node 0 1 2 3
0: 10 21 21 32
1: 21 10 32 21
2: 21 32 10 21
3: 32 21 21 10
From: Jianguo Wu wujian...@huawei.com
Hi all,
When doing memory-hot-plug, We found node distance is wrong after
offline
a node in IA64 platform. For example system has 4 nodes:
node distances:
node 0 1 2 3
0: 10 21 21 32
1: 21 10 32 21
2: 21 32 10 21
3: 32
From: Jianguo Wu wujian...@huawei.com
Hi all,
I found following definition in include/linux/memory.h, in my IA64
platform, SECTION_SIZE_BITS is equal to 32, and MIN_MEMORY_BLOCK_SIZE will be 0.
#define MIN_MEMORY_BLOCK_SIZE (1 SECTION_SIZE_BITS)
Because
28 matches
Mail list logo
