All of lore.kernel.org
 help / color / mirror / Atom feed
From: Branimir Maksimovic <branimir.maksimovic@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: 15995MB available under Linux but 16329MB available under Win 7
Date: Sat, 22 Mar 2014 05:35:39 +0100	[thread overview]
Message-ID: <532D131B.1050606@gmail.com> (raw)

This really puzzles me.

bmaxa@maxa:~$ lspci -v -s 01:00.0
01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 
560 Ti] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: CardExpert Technology Device 0801
     Flags: bus master, fast devsel, latency 0, IRQ 52
     Memory at f4000000 (32-bit, non-prefetchable) [size=32M]
     Memory at e8000000 (64-bit, prefetchable) [size=128M]
     Memory at f0000000 (64-bit, prefetchable) [size=64M]
     I/O ports at e000 [size=128]
     [virtual] Expansion ROM at f6000000 [disabled] [size=512K]
     Capabilities: <access denied>
     Kernel driver in use: nvidia

bmaxa@maxa:~$ dmesg | grep Mem
[    0.000000] Memory: 16358808K/16721316K available (7232K kernel code, 
1106K rwdata, 3456K rodata, 1324K init, 1432K bss, 362508K reserved)

Everything is clear most of reserved RAM goes to VGA mapping?

But, Windows resource monitor and task manager says just around 50MB
hardware reserved?

So I have tried different kernel boot parameters to no avail.
So question is: Does Windows magically maps VGA to upper addresses 
(beyond 16GB)
or simply Windows does not reports all reserved RAM?

When I disable memory remap in BIOS Windows reports 500MB more reserved,
but Linux adds this 500MB to 300MB reserved giving around 800MB.

CPU is i5 3570k, motherboard z77, 16GB of DD3 RAM, AMI BIOS.

Branimir.


             reply	other threads:[~2014-03-22  4:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-22  4:35 Branimir Maksimovic [this message]
2014-03-22  6:03 ` 15995MB available under Linux but 16329MB available under Win 7 Robert Hancock
2014-03-22  6:16   ` Branimir Maksimovic
2014-03-22  6:41     ` Robert Hancock

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=532D131B.1050606@gmail.com \
    --to=branimir.maksimovic@gmail.com \
    --cc=linux-kernel@vger.kernel.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.