kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: haojian.zhuang@gmail.com (Haojian Zhuang)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Missing 1GB RAM, where is it?
Date: Fri, 15 Apr 2011 08:45:53 +0800	[thread overview]
Message-ID: <BANLkTimGbqUXArFGXYbs_qVTWSU=HE3VMg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinonV2MGP4rWUKX+Tx4WvMurxwowA@mail.gmail.com>

On Fri, Apr 15, 2011 at 12:12 AM, Haojian Zhuang
<haojian.zhuang@gmail.com> wrote:
> On Thu, Apr 14, 2011 at 11:43 PM, Andrzej Kardas <andrzej-kardas@o2.pl> wrote:
>>
>>
>> On 14.04.2011 17:09, Adrian Cornish wrote:
>>
>> Just a thought - lower end graphic cards use system RAM as their own
>> dont they
>>
>> You right, devices like graphic card, ethernet cards etc. are mapped into
>> memory, what cause some amount RAM is not available for system use. But as
>> i've wrote before, i'm wondering why addresses in /proc/iomem (where the map
>> of memory is) are not contiguous. I think, there should be info about what
>> region of memory is mapped where (BIOS, PCI bus, for system use etc) for
>> whole 4GB (Am I right??) address space (for 32bit OS). Instead of that,
>> there are small "holes" in addresses and the total size of this holes (in my
>> case) is about 400MB. So i wonder where that memory is.
>>
> What you see from /proc/iomem is virtual address. For the 32-bit
> system, it's 4GB size.
> Virtual address needn't be sorted one by one.
>
> You have 4GB physical memory. But only a part is mapped linearly in
> virtual address.
> They're called lowmem. The rest are used as highmem what can be
> allocated by device
> driver or applications. Kernel needs to map it first before accessing highmem.
>
> CPU's MMU manages the mapping table between virtual address and
> physical address.
>
Oh, my inputs are wrong. Please ignore it. I messed something. What we saw
should be physical memory. I think the real hardware should be accessed by
36-bit, not 32-bit.
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org
>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>
>>
>

  reply	other threads:[~2011-04-15  0:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-12 16:06 Enabling Signals in kernel Vijay Ram Chitrapu
2011-04-13  1:01 ` Haojian Zhuang
2011-04-13 19:30   ` julie Sullivan
2011-04-13 17:20 ` Missing 1GB RAM, where is it? Andrzej Kardas
2011-04-14  2:42   ` Mulyadi Santosa
2011-04-14 11:27     ` andrzej-kardas
2011-04-14 12:17       ` Mulyadi Santosa
2011-04-14 15:23         ` Andrzej Kardas
2011-04-16  6:07           ` Mulyadi Santosa
2011-04-14 15:09   ` Adrian Cornish
2011-04-14 15:43     ` Andrzej Kardas
2011-04-14 16:12       ` Haojian Zhuang
2011-04-15  0:45         ` Haojian Zhuang [this message]
     [not found]       ` <BANLkTik7g8vEf6X+suzwbXD1b4ow1__2xQ@mail.gmail.com>
2011-04-17  7:58         ` Missing 1GB RAM, where is it? - SUMMARY Andrzej Kardas
2011-04-17 15:31           ` julie Sullivan
2011-04-18 10:17             ` andrzej-kardas

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='BANLkTimGbqUXArFGXYbs_qVTWSU=HE3VMg@mail.gmail.com' \
    --to=haojian.zhuang@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).