This patch creates an additional zone, ZONE_MOVABLE. This zone is only
usable by allocations which specify both __GFP_HIGHMEM and __GFP_MOVABLE.
Hot-added memory continues to be placed in their existing destination as
there is no mechanism to redirect them to a specific zone.
Signed-off-by:
This patch creates an additional zone, ZONE_MOVABLE. This zone is only
usable by allocations which specify both __GFP_HIGHMEM and __GFP_MOVABLE.
Hot-added memory continues to be placed in their existing destination as
there is no mechanism to redirect them to a specific zone.
Signed-off-by:
On (26/01/07 09:16), Christoph Lameter didst pronounce:
> I do not see any updates of vmstat.c and vmstat.h. This
> means that VM statistics are not kept / considered for ZONE_MOVABLE.
Based on searching around for ZONE_DMA32, the following patch appears to be
all that is required;
diff -rup -X
On Fri, 26 Jan 2007, Christoph Lameter wrote:
On Thu, 25 Jan 2007, Mel Gorman wrote:
@@ -166,6 +168,8 @@ enum zone_type {
#define ZONES_SHIFT 1
#elif __ZONE_COUNT <= 4
#define ZONES_SHIFT 2
+#elif __ZONE_COUNT <= 8
+#define ZONES_SHIFT 3
#else
You do not need a shift of 3. Even with
On Fri, 26 Jan 2007, Christoph Lameter wrote:
On Thu, 25 Jan 2007, Mel Gorman wrote:
@@ -166,6 +168,8 @@ enum zone_type {
#define ZONES_SHIFT 1
#elif __ZONE_COUNT = 4
#define ZONES_SHIFT 2
+#elif __ZONE_COUNT = 8
+#define ZONES_SHIFT 3
#else
You do not need a shift of 3. Even with
On (26/01/07 09:16), Christoph Lameter didst pronounce:
I do not see any updates of vmstat.c and vmstat.h. This
means that VM statistics are not kept / considered for ZONE_MOVABLE.
Based on searching around for ZONE_DMA32, the following patch appears to be
all that is required;
diff -rup -X
On Fri, 26 Jan 2007, Christoph Lameter wrote:
On Fri, 26 Jan 2007, Mel Gorman wrote:
Other than adding some TEXT_FOR_MOVABLE, an addition to TEXTS_FOR_ZONES() and
similar updates for FOR_ALL_ZONES(), what code in there uses special awareness
of the zone?
Look for special handling of
On Fri, 26 Jan 2007, Christoph Lameter wrote:
I do not see any updates of vmstat.c and vmstat.h. This
means that VM statistics are not kept / considered for ZONE_MOVABLE.
hmm, dirt.
Other than adding some TEXT_FOR_MOVABLE, an addition to TEXTS_FOR_ZONES()
and similar updates for
On Fri, 26 Jan 2007, Mel Gorman wrote:
> Other than adding some TEXT_FOR_MOVABLE, an addition to TEXTS_FOR_ZONES() and
> similar updates for FOR_ALL_ZONES(), what code in there uses special awareness
> of the zone?
Look for special handling of ZONE_DMA32 and you will find what you are
looking
I do not see any updates of vmstat.c and vmstat.h. This
means that VM statistics are not kept / considered for ZONE_MOVABLE.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Fri, 26 Jan 2007, Christoph Lameter wrote:
On Thu, 25 Jan 2007, Mel Gorman wrote:
@@ -166,6 +168,8 @@ enum zone_type {
#define ZONES_SHIFT 1
#elif __ZONE_COUNT <= 4
#define ZONES_SHIFT 2
+#elif __ZONE_COUNT <= 8
+#define ZONES_SHIFT 3
#else
You do not need a shift of 3. Even with
On Thu, 25 Jan 2007, Mel Gorman wrote:
> @@ -166,6 +168,8 @@ enum zone_type {
> #define ZONES_SHIFT 1
> #elif __ZONE_COUNT <= 4
> #define ZONES_SHIFT 2
> +#elif __ZONE_COUNT <= 8
> +#define ZONES_SHIFT 3
> #else
You do not need a shift of 3. Even with ZONE_MOVABLE the maximum
number of
On Thu, 25 Jan 2007, Mel Gorman wrote:
@@ -166,6 +168,8 @@ enum zone_type {
#define ZONES_SHIFT 1
#elif __ZONE_COUNT = 4
#define ZONES_SHIFT 2
+#elif __ZONE_COUNT = 8
+#define ZONES_SHIFT 3
#else
You do not need a shift of 3. Even with ZONE_MOVABLE the maximum
number of zones is
On Fri, 26 Jan 2007, Christoph Lameter wrote:
On Thu, 25 Jan 2007, Mel Gorman wrote:
@@ -166,6 +168,8 @@ enum zone_type {
#define ZONES_SHIFT 1
#elif __ZONE_COUNT = 4
#define ZONES_SHIFT 2
+#elif __ZONE_COUNT = 8
+#define ZONES_SHIFT 3
#else
You do not need a shift of 3. Even with
I do not see any updates of vmstat.c and vmstat.h. This
means that VM statistics are not kept / considered for ZONE_MOVABLE.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Fri, 26 Jan 2007, Christoph Lameter wrote:
I do not see any updates of vmstat.c and vmstat.h. This
means that VM statistics are not kept / considered for ZONE_MOVABLE.
hmm, dirt.
Other than adding some TEXT_FOR_MOVABLE, an addition to TEXTS_FOR_ZONES()
and similar updates for
On Fri, 26 Jan 2007, Mel Gorman wrote:
Other than adding some TEXT_FOR_MOVABLE, an addition to TEXTS_FOR_ZONES() and
similar updates for FOR_ALL_ZONES(), what code in there uses special awareness
of the zone?
Look for special handling of ZONE_DMA32 and you will find what you are
looking for.
On Fri, 26 Jan 2007, Christoph Lameter wrote:
On Fri, 26 Jan 2007, Mel Gorman wrote:
Other than adding some TEXT_FOR_MOVABLE, an addition to TEXTS_FOR_ZONES() and
similar updates for FOR_ALL_ZONES(), what code in there uses special awareness
of the zone?
Look for special handling of
This patch creates an additional zone, ZONE_MOVABLE. This zone is only
usable by allocations which specify both __GFP_HIGHMEM and __GFP_MOVABLE.
Hot-added memory continues to be placed in their existing destination as
there is no mechanism to redirect them to a specific zone.
Signed-off-by:
This patch creates an additional zone, ZONE_MOVABLE. This zone is only
usable by allocations which specify both __GFP_HIGHMEM and __GFP_MOVABLE.
Hot-added memory continues to be placed in their existing destination as
there is no mechanism to redirect them to a specific zone.
Signed-off-by:
20 matches
Mail list logo
