View Single Post
  #2  
Old April 12th 15, 09:22 PM posted to alt.comp.periphs.videocards.nvidia
Paul
external usenet poster
 
Posts: 13,364
Default nvidia GTX 970 4 GiB stuffup

wrote:
So these cards have 3.5 GiB and 0.5 GiB of memory.
We went throught this about 10 years ago with Intel northbridge,
where a 32-bit Windows saw typically 3.25 GiB with 4 GiB installed.
If you had PAE linux, you got almost 4 GiB, but not continuous.
Didn't nvidia learn from history? Repeat!


That's not exactly true. The card in question has
one (or more) functional units turned off (for yield reasons),
preventing the memory interface unit for it from
working. There really is only 3.5GiB of memory.
None hidden. Not a PAE issue. The GPU ends up having
a weird number of memory interfaces on the side of
it, that leads to the 3.5GiB number.

The NVidia marketing department failed to get the
details right. And nobody technical caught the mistake
until it turned into a public relations disaster.

And obviously, for such a humongous card, you cannot
use a 32 bit Windows OS. There would simply be no
address space left over to allow the OS to run. And
this is caused by the Windows (address space limiting)
memory license for 32 bit Windows. PAE is enabled,
but only Ring0 code is allowed to use the entire space.
Applications running in Ring3 on a Windows 32 bit OS,
are not allowed outside the 4GB "box".

That large of a card, would mean practically none of
the system memory would be mapped, and Windows would
have no place to run. A 32 bit OS should really crash,
if that card had just been plugged in.

As an example, I run WinXP SP3 x32 for my "typing machine".
I have 8GB of RAM installed. Windows uses 4GB (minus
bus addresses of around 0.5GB). I have a RAMDisk which
uses the other 4GB. All 8GB are in usage right now.
(WinXP SP3 x32 has PAE enabled by default, for NX bit usage.)
The RAMDisk code is implemented as a "driver" and
lives in Ring0 with the kernel code, which is how
memory outside the licensed region can be accessed.
The code is not being used by a "program" (Ring3),
but is being used by a "driver" (Ring0), and that
is how the Windows memory license is partially
being bypassed.

I didn't buy the RAM solely for WinXP. Sometimes
I boot up the paid-for Windows 8.1 on this
machine, and then the entire memory can be
used by programs. So it's not totally lost.

And the RAMDisk idea is great. I use it for
unzipping large packages, ones that would really
fragment a hard drive. So if I unzip the source
for Thunderbird program, which is 125,000 files,
I keep them on the RAMDisk, which isn't slowed in
the least by fragmentation. In HDTune, the RAMDisk
has a bandwidth of slightly less than 4GB/sec.

(Look for "RAMDisk Lite", if your machine has more RAM
than a 32 bit OS can use. The free version can only use 4GB
of left-over RAM, while the paid version is likely to map
as much as 60GB or so. It's possible the PAE limit varies
with OS version. Something later than WinXP x32 might be
able to do more with PAE.)

http://memory.dataram.com/products-a...ftware/ramdisk

Paul