I am curious about the limitation of 32bit architectures. From what I understand, a 32 digit (bits) binary number can only go up to 2^32 = 4 294 967 296. It is then easy to figure outthat if a 32 bit processor uses 32bits to store data address in memory, it can only go as high as 4.2 billion which is where the 4GB limitation comes from.
Now here's my problem. I come from a C environment and I know that such a problem is usually fixed by encoding the address on multiple adjascent '32bit-spaces'. So I'm guessing I have the whole thing figured out wrong.
Can anyone explain (or at least point me in the direction of a post/article/tutorial that does) the limitations of 32 bit operating systems as well as the actual need for 64 bits, except that we're all attracted to shiny high numbers?
If anyone also cares to comment about the use of 32 bit OS on 64 bit proc and whether there's a loss in performance.
Thanks ;)
Now here's my problem. I come from a C environment and I know that such a problem is usually fixed by encoding the address on multiple adjascent '32bit-spaces'. So I'm guessing I have the whole thing figured out wrong.
Can anyone explain (or at least point me in the direction of a post/article/tutorial that does) the limitations of 32 bit operating systems as well as the actual need for 64 bits, except that we're all attracted to shiny high numbers?
If anyone also cares to comment about the use of 32 bit OS on 64 bit proc and whether there's a loss in performance.
Thanks ;)