Hi Andrew,
On 01/26/2013 08:36 AM, Andrew Morton wrote:
The patch generates a bunch of rejects, partly due to linux-next
changes but I think I fixed everything up OK.
Thank you for your fixing. :)
index 4ddf497..f841d0e 100644
--- a/arch/x86/mm/srat.c
+++ b/arch/x86/mm/srat.c
@@ -141,11
Hi Andrew,
On 01/26/2013 08:36 AM, Andrew Morton wrote:
The patch generates a bunch of rejects, partly due to linux-next
changes but I think I fixed everything up OK.
Thank you for your fixing. :)
index 4ddf497..f841d0e 100644
--- a/arch/x86/mm/srat.c
+++ b/arch/x86/mm/srat.c
@@ -141,11
On Fri, 25 Jan 2013 17:42:08 +0800
Tang Chen wrote:
> When implementing movablemem_map boot option, we introduced an array
> movablemem_map.map[] to store the memory ranges to be set as ZONE_MOVABLE.
>
> Since ZONE_MOVABLE is the latst zone of a node, if user didn't specify
> the whole node
When implementing movablemem_map boot option, we introduced an array
movablemem_map.map[] to store the memory ranges to be set as ZONE_MOVABLE.
Since ZONE_MOVABLE is the latst zone of a node, if user didn't specify
the whole node memory range, we need to extend it to the node end so that
we can
When implementing movablemem_map boot option, we introduced an array
movablemem_map.map[] to store the memory ranges to be set as ZONE_MOVABLE.
Since ZONE_MOVABLE is the latst zone of a node, if user didn't specify
the whole node memory range, we need to extend it to the node end so that
we can
On Fri, 25 Jan 2013 17:42:08 +0800
Tang Chen tangc...@cn.fujitsu.com wrote:
When implementing movablemem_map boot option, we introduced an array
movablemem_map.map[] to store the memory ranges to be set as ZONE_MOVABLE.
Since ZONE_MOVABLE is the latst zone of a node, if user didn't specify
6 matches
Mail list logo