On 08/15/2013 05:54 AM, Naoya Horiguchi wrote:
> On Thu, Aug 08, 2013 at 06:16:17PM +0800, Tang Chen wrote:
>> --- a/mm/memblock.c
>> +++ b/mm/memblock.c
> ...
>> @@ -719,6 +723,10 @@ void __init_memblock __next_free_mem_range_rev(u64
>> *idx, int nid,
>> if (nid != MAX_NUMNODES&&
On Thu, Aug 08, 2013 at 06:16:17PM +0800, Tang Chen wrote:
> --- a/mm/memblock.c
> +++ b/mm/memblock.c
...
> @@ -719,6 +723,10 @@ void __init_memblock __next_free_mem_range_rev(u64 *idx,
> int nid,
> if (nid != MAX_NUMNODES && nid != memblock_get_region_node(m))
>
On Thu, Aug 08, 2013 at 06:16:17PM +0800, Tang Chen wrote:
--- a/mm/memblock.c
+++ b/mm/memblock.c
...
@@ -719,6 +723,10 @@ void __init_memblock __next_free_mem_range_rev(u64 *idx,
int nid,
if (nid != MAX_NUMNODES nid != memblock_get_region_node(m))
On 08/15/2013 05:54 AM, Naoya Horiguchi wrote:
On Thu, Aug 08, 2013 at 06:16:17PM +0800, Tang Chen wrote:
--- a/mm/memblock.c
+++ b/mm/memblock.c
...
@@ -719,6 +723,10 @@ void __init_memblock __next_free_mem_range_rev(u64
*idx, int nid,
if (nid != MAX_NUMNODES nid !=
Linux kernel cannot migrate pages used by the kernel. As a result, hotpluggable
memory used by the kernel won't be able to be hot-removed. To solve this
problem, the basic idea is to prevent memblock from allocating hotpluggable
memory for the kernel at early time, and arrange all hotpluggable
Linux kernel cannot migrate pages used by the kernel. As a result, hotpluggable
memory used by the kernel won't be able to be hot-removed. To solve this
problem, the basic idea is to prevent memblock from allocating hotpluggable
memory for the kernel at early time, and arrange all hotpluggable
6 matches
Mail list logo