Linked by Thom Holwerda on Wed 5th Jan 2011 22:09 UTC
Thread beginning with comment 456197
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
...but since developers already have issues with multiple threads I don't see this happening soon...
So perhaps we're moving to 64-bit for simplicity, not necessity.
So perhaps we're moving to 64-bit for simplicity, not necessity.
Well, I wouldn't bother going 64-bit if it wasn't
1/A priori faster and certainly easier to use than 32-bit + PAE (no need to have the OS juggle with your data so that it fits in your 32-bit address space)
2/Much, much more convenient on x86 (AMD have taken the opportunity of AMD64 to clean up part of x86's legacy mess, so x86 processors are easier to play with in 64-bit mode ^^)
Edited 2011-01-06 17:42 UTC




Member since:
2005-12-04
A single process can use AWE to map subsets of data in its limited address space at a time while still using more than 32-bits of physical memory. Or, in many cases, it can delegate that job to the operating system (eg. by using the OS file cache, which is not limited to the process' 4Gb limit.)
So perhaps we're moving to 64-bit for simplicity, not necessity.