From: "Chris Friesen" <cfriesen@nortel.com>
To: linuxppc-dev@ozlabs.org
Subject: kernel memory map/usage/holes?
Date: Mon, 17 Jul 2006 14:06:57 -0600 [thread overview]
Message-ID: <44BBEDE1.3040004@nortel.com> (raw)
I've got a Maple board with 4GB of memory running a modified 2.6.10
kernel. When it boots, I see the following in the logs:
Top of RAM: 0x180000000, Total RAM: 0x100000000
On node 0 totalpages: 1048576
DMA zone: 1048576 pages, LIFO batch:16
Normal zone: 0 pages, LIFO batch:1
HighMem zone: 0 pages, LIFO batch:1
Then a bit later, I see:
Memory: 4006976k/6291456k available (3408k kernel code, 2284124k
reserved, 1656k data, 448k bss, 220k init)
1048576 pages works out to 4194304kB, so what happened to the 187328kB
that is the difference between the "Total RAM" and "Memory:" lines?
We've got an app that wants as much memory as possible, so I need to
explain where this 183MB of memory is being used.
Thanks,
Chris
next reply other threads:[~2006-07-17 20:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 20:06 Chris Friesen [this message]
2006-07-19 4:47 ` kernel memory map/usage/holes? Sonny Rao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44BBEDE1.3040004@nortel.com \
--to=cfriesen@nortel.com \
--cc=linuxppc-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.