36 bit VS 64 bit drivers for graphics card?

pArTy

Limp Gawd
Joined
Jul 21, 2004
Messages
433
Does 64bit drivers use 2X the memory 32bit drivers would use for are video cards? So if a game comes out thats 64bit and my card is 512mb. That means it would act like a 256mb unless it was a 32bit game/driver. Am I right? :(
 
Does 64bit drivers use 2X the memory 32bit drivers would use for are video cards? So if a game comes out thats 64bit and my card is 512mb. That means it would act like a 256mb unless it was a 32bit game/driver. Am I right? :(

No. Though i can see why you'd think that. The memory on a video card is mostly used for textures and frame buffers which don't double in size just because the program is 64-bit. The textures don't increase in resolution, or size.

Anyone else expand? I'm a little rusty on 32-bit vs 64-bit program system memory usage as well as video card memory....
 
video card memory has nothing to do with the 32bit/64bit. the 32/64bit are if the cpu will run in 32 or 64 bit proccesing. most programs now use 32bit,but 64bit will become more common when vista is out.
 
No. Though i can see why you'd think that. The memory on a video card is mostly used for textures and frame buffers which don't double in size just because the program is 64-bit. The textures don't increase in resolution, or size.

Anyone else expand? I'm a little rusty on 32-bit vs 64-bit program system memory usage as well as video card memory....
I'll offer a few words about it:

The word size of a machine (ie 32- or 64-bit) is the size of a basic unit of data. If your word size is 64-bits for example, then your pointers are going to be 8 bytes in size, which means the size of your address space is 2^64. Also the largest unsigned integer the system can deal with is (2^64 - 1). On a 64-bit system you can deal with larger integers (without resorting to doing the math in software), and you've got a big address space to play in.

As for comparing memory usage between 32- and 64-bit systems, memory usage falls into two categories: code and data. Taking a quick look at each:

Code: 64-bit code is liable to be slightly larger than equivalent 32-bit code, but not twice as large. Machine code may contain literal (constant) 64-bit values. I.e. "x = 10" where x is a 64-bit word, so 64-bit code will obviously gain an extra 4 bytes whenever such constants are specified in the code. I'm not actually sure how much the code tends to bloat (on average) going from 32- to 64-bit, my guess is something like 10-20%, but definitely not 100%. I believe you'd see a whole lot more bloat in the code size going from CISC => RISC (w/o changing the word size).

Data: As I said above, 64-bit code can easily deal with 64-bit integers, but you don't have to use 64-bit integers, you can still use 32-bit (or 16-bit, or 8-bit) integers. And you can still do a good job of packing data in memory, to minimize the waste. Pointers are always 8-bytes however, so whenever you store a pointer in memory, that is using 8 bytes whereas it would use 4 bytes on a 32-bit system. Also addresses are often aligned to a "word boundary" (i.e. 8, 16, 24, 32, etc... on a 64-bit system), and that will lead to some bloat in the data also. Bottom line: again, not 100% more memory use, more like a small-ish percentage increase.

And in any case, your decision about 32-bit versus 64-bit drivers is already made when you have decided on 32-bit versus 64-bit Vista :)
 
Back
Top