I recently changed plat_mem_setup() or equivalent in my platform code to not mark the first 32M of memory as BOOT_MEM_ROM_DATA and instead have the first BOOT_MEM_RAM memory region start at 0. Here is the two lines of output from mem_init() for the two different versions: Memory: 433408k/475136k available (2202k kernel code, 41556k reserved, 690k data, 112k init, 0k highmem) Memory: 433408k/507904k available (2202k kernel code, 74324k reserved, 689k data, 112k init, 0k highmem) As you can see, the 32M got added to "reserved" memory (?) and only added to the right hand number of the "available". OK, so what does that mean? I promised our monkey userspace programmers that they would have another 32M of memory to slosh around in, but before I release this change on them I'd like to know what these numbers are telling me. This is on 2.6.22 from l.m.o on a Sibyte 1125 in 64bit LE. CONFIG_FLATMEM=y which was the fashion at the time. Cheers, a
