20 Jun
2011
20 Jun
'11
11:11 a.m.
On 20/06/11 13:00, Andy Smith wrote:
Hi OM,
On Mon, Jun 20, 2011 at 12:40:48PM +0200, Ole-Morten Duesund wrote:
In that case, my debian "eats" memory too.
Perhaps this might be relevant? From my dmesg :
[21532581.898890] Initializing CPU#0
[21532581.902734] Initializing HighMem for node 0 (00000000:00000000)
[21532581.902740] Memory: 338928k/368640k available (2573k kernel code,
29052k reserved, 1394k data, 396k init, 0k highmem)
[21532581.902746] virtual kernel memory layout:
[21532581.902747] fixmap : 0xf5556000 - 0xf57ff000 (2724 kB)
[21532581.902748] pkmap : 0xf5000000 - 0xf5200000 (2048 kB)
[21532581.902749] vmalloc : 0xd7000000 - 0xf4ffe000 ( 479 MB)
[21532581.902751] lowmem : 0xc0000000 - 0xd6800000 ( 360 MB)
[21532581.902752] .init : 0xc13e0000 - 0xc1443000 ( 396 kB)
[21532581.902753] .data : 0xc1283475 - 0xc13dfeb0 (1394 kB)
[21532581.902754] .text : 0xc1000000 - 0xc1283475 (2573 kB)
…
[21532582.564578] Unpacking initramfs...
[21532582.582204] Freeing initrd memory: 19440k freed
So, on boot about 29MB is reserved, and then 19MB is freed, which leaves
me 10MB "short"
The "virtual kernel memory layout" seems to sum nicely up to about 10M,
might that be it?
- OM
$ free -m
total used free shared buffers cached
Mem: 350 345 5 0 22 90
-/+ buffers/cache: 232 118
Swap: 299 87 212
But I'm suddenly unsure if it should say 360 or if 350 is correct?
360M would correspond to a sum of RAM that we would usually sell, so
is most likely what it "should" be.