Re: [PATCH 0/7] [RFC] Sizing zones and holes in an architecture independent manner V2
- From: mel@xxxxxxxxx (Mel Gorman)
- Date: Thu, 13 Apr 2006 18:30:08 +0100
On (13/04/06 10:19), Luck, Tony didst pronounce:
On Thu, Apr 13, 2006 at 10:52:08AM +0100, Mel Gorman wrote:
I didn't look at the test program output carefully enough! There was a
double counting of some holes because of a missing "if" - obvious in the
morning. Fix is this (applies on top of the debugging patch)
Back to not booting with tiger_defconfig on Intel Tiger box :-(
There are no lines like:
On node 0 totalpages: 260725
DMA zone: 129700 pages, LIFO batch:7
Normal zone: 131025 pages, LIFO batch:7
in the log ... which might explain the OOM later.
Whole console log appended (The "Kill process 2" messages repeat
forever).
-Tony
<SNIP>
Dumping sorted node map
entry 0: 0 1024 -> 130688
entry 1: 0 130984 -> 131020
entry 2: 0 393216 -> 524164
entry 3: 0 524192 -> 524269
Hole found index 1: 130688 -> 130984
Hole found index 2: 131020 -> 262144
Hole found index 2: 131020 -> 393216
Double counted a hole here, then went downhill. Does the following fix
it?
diff -rup -X /usr/src/patchset-0.5/bin//dontdiff linux-2.6.17-rc1-zonesizing-v6/mm/mem_init.c linux-2.6.17-rc1-107-debug/mm/mem_init.c
--- linux-2.6.17-rc1-zonesizing-v6/mm/mem_init.c 2006-04-13 10:30:50.000000000 +0100
+++ linux-2.6.17-rc1-107-debug/mm/mem_init.c 2006-04-13 18:00:39.000000000 +0100
@@ -753,17 +753,21 @@ unsigned long __init zone_absent_pages_i
start_pfn = early_node_map[i].start_pfn;
if (start_pfn > arch_zone_highest_possible_pfn[zone_type])
start_pfn = arch_zone_highest_possible_pfn[zone_type];
- if (prev_end_pfn > start_pfn) {
- printk("prev_end > start_pfn : %lu > %lu\n",
- prev_end_pfn,
- start_pfn);
- BUG();
- }
+ if (prev_end_pfn < arch_zone_lowest_possible_pfn[zone_type])
+ prev_end_pfn = arch_zone_lowest_possible_pfn[zone_type];
/* Update the hole size cound and move on */
- hole_pages += start_pfn - prev_end_pfn;
- printk("Hole found index %d: %lu -> %lu\n",
- i, prev_end_pfn, start_pfn);
+ if (start_pfn > arch_zone_lowest_possible_pfn[zone_type]) {
+ if (prev_end_pfn > start_pfn) {
+ printk("prev_end > start_pfn : %lu > %lu\n",
+ prev_end_pfn,
+ start_pfn);
+ BUG();
+ }
+ hole_pages += start_pfn - prev_end_pfn;
+ printk("Hole found index %d: %lu -> %lu\n",
+ i, prev_end_pfn, start_pfn);
+ }
prev_end_pfn = early_node_map[i].end_pfn;
}
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- [PATCH 0/7] [RFC] Sizing zones and holes in an architecture independent manner V2
- From: Mel Gorman
- Re: [PATCH 0/7] [RFC] Sizing zones and holes in an architecture independent manner V2
- From: Mel Gorman
- Re: [PATCH 0/7] [RFC] Sizing zones and holes in an architecture independent manner V2
- From: Luck, Tony
- [PATCH 0/7] [RFC] Sizing zones and holes in an architecture independent manner V2
- Prev by Date: Re: lockd oopses continue with 2.6.16.1
- Next by Date: Re: [PATCH] [2/2] POWERPC: Lower threshold for DART enablement to 1GB, V2
- Previous by thread: Re: [PATCH 0/7] [RFC] Sizing zones and holes in an architecture independent manner V2
- Next by thread: Re: [PATCH 0/7] [RFC] Sizing zones and holes in an architecture independent manner V2
- Index(es):
Relevant Pages
|
