As far as I know CUDA is 64bit, and you should be able to run CUDA on tegra2. So, for ARM the only reason to have 64bit is to address large memory, and drive c

As far as I know CUDA is 64bit, and you should be able to run CUDA on tegra2. So, for ARM the only reason to have 64bit is to address large memory, and drive controllers for flash can address the rest. heck if someone really wanted to do an integrated server environment they could put ram behind the drive controller. So having a 32bit core and a 64bit gpu on chip means you can do complex scientific math, but how many web apps really need 64bit floats, ints? In a web world if you needed 64bit, just make a service on a platform that works and either proxy the request or redirect to it. i guess mongodb would suck on a 32bit arm, but that's just because they have a lazy memory manager model. i am sure if arm got big or if someone paid 10gen to fix it, they would. I bet most of the web could work on a large array of high frequency ARM chips. I know that both google is working on it, and I have seen articles on facebook doing it. It's definitely experimental right now, but I think in the next 18 months you will see more public experiments. Mobile chips also have better power management than x86, and can go in to deep sleep and maintain cache really well. Watch this, i know it's going to POP. there is also evidence that nVidia is figuring out it's legal strategy for this. which has an ARM license, and bought transmeta.