lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 09 May 2011 02:18:26 +0800
From:	microcai <microcaicai@...il.com>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: [Question] Where is the missing 384k? Please, I've searching for
 it years!

It's being too long since I got this question.
I have to ask, even with a chance that I am considered as spam, and be
banned by kernel.org, I have to ask.
Please CC me if any one is going to answer my questions, I'll be
appreciate if you solve my haze.

So, my question is really simple, where is the missing 384k RAM?

When I read the books about PC, or see the output of dmesg, I've always
told that, 640k-1M is reserved for BIOS, and should not be used.

1)
384k RAM is reserved because BIOS is there. But I've heard that BIOS is
really in a ROM, not in RAM. So, where is the RAM when CPU is addressing
the ROM? Does the ROM just override the RAM and makes the RAM completely
un-addressable? What if people just got 2MB RAM? 384k of 2MB RAM is a
lot of wast!

2)
Is there a way to unmap the ROM and get back the RAM? or remap the 384k
RAM to upper address? If there is , why don't the kernel use this and
get my RAM(which is money) back?

3)
If there is not way to unmap the ROM or remap the RAM, why do they wast
384k RAM there! Even if 4G RAM is common now, 2M RAM is common in the
old days. Why did they do that!


Please help me to erase the big big question mark in my hart, Thanks!


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ