Please refer to my other messages regarding the true purposes of the
tree-based bootmem and so on.
Given that it's one architecture, a single very small machine, and one
kernel version, this is perhaps not as scientific as I'd like it to be,
but my personal computer (i386) at home shows the following results for
2.4.17-rc2 and my local patch set (plus or minus bootmem).
2.4.17-rc2-wli-bootmem:
Memory: 769332k/786368k available
(1389k kernel code, 16648k reserved, 1019k data, 224k init, 0k highmem)
2.4.17-rc2-wli:
Memory: 769340k/786368k available
(1389k kernel code, 16640k reserved, 1019k data, 216k init, 0k highmem)
After freeing init, the total memory is identical, not my expected 8KB:
--- bootmem.meminfo Fri Dec 21 03:33:44 2001
+++ nobootmem.meminfo Fri Dec 21 03:30:53 2001
@@ -1,18 +1,18 @@
total: used: free: shared: buffers: cached:
-Mem: 788025344 78618624 709406720 0 5652480 33247232
+Mem: 788025344 87261184 700764160 0 12656640 34500608
Swap: 518152192 0 518152192
MemTotal: 769556 kB
-MemFree: 692780 kB
+MemFree: 684340 kB
MemShared: 0 kB
-Buffers: 5520 kB
-Cached: 32468 kB
+Buffers: 12360 kB
+Cached: 33692 kB
SwapCached: 0 kB
-Active: 53784 kB
-Inact_dirty: 4748 kB
+Active: 61728 kB
+Inact_dirty: 4876 kB
Inact_clean: 0 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 769556 kB
-LowFree: 692780 kB
+LowFree: 684340 kB
SwapTotal: 506008 kB
SwapFree: 506008 kB
Cheers,
Bill
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/