no. 128 bit is not yet possible. It will take a whole new instruction set redesign to get 128 bit. maybe windows 10 or 11. Even then it will be 64 or 128, just like 32 or 64 now.Will Windows 8 require a 128-bit CPU in order to run or does anybody know for sure?
Thank you
m$ will not be able to beat linux to 128 bit.
Th 8086 was 16-bit but it had a 20-bit address bus. With 16 bits you could address only 64KB RAM but I'm not aware of any CPUs that could address only 64KB of RAM (that of course doesn't mean they don't exist, I just never heard of any). With 8 bits you cousd only address 256 bytes (not MB or KB, just plain bytes). The memory you can address with a given number of bits is given by 2^n where n is the number of bits (and ^ means exponent).What can 8-bit (say a 6502) and 16-bit (what processors were 16-bit?) read to a maximum of then?
I'm pretty sure there's no 64-bit ARM CPUs out there, ARMv8 is the newest version and has support for 64-bit but I don't think any CPUs based on that core have been shipped yet (or if they are they are far from being majority). In any event, they certainly won't run x86-64 code.it requires 32 or 64 bit to run. Most, if not all of the ARM processors that run smart phones these days are x86-64.
Theoretical maximum for most x86 CPUs is 64GB with PAE. Most current operating systems use PAE (Windows has since XP but most editions limit the physical address space to 4GB anyway).x86 (32 bit) can read to a maximum theoritical level of 4GB of RAM
What do you mean by faster?the higher the Bit rate, the more memory can be addressed, and the faster it can be addressed.
You can't address any more of it at once - you can only address one memory location at once, and it's done in a single cycle regardless of whether it's x86 or x64 (well, since the 386 anyway).by faster i mean more of it is addressed at once.
basically, meaning a higher bandwidth with memory addresses.
Well, to move 64 bits with a 32bit-command, you need to call it twice. In 64bit you need to call it once.You can't address any more of it at once - you can only address one memory location at once, and it's done in a single cycle regardless of whether it's x86 or x64 (well, since the 386 anyway).
I would call it a practical maximum. It is the way PAE is implemeneted that limits it to 64 GB. Modern 64bit CPUs have a much higher limitation.Theoretical maximum for most x86 CPUs is 64GB with PAE.
Well, to move 64 bits with a 32bit-command, you need to call it twice. In 64bit you need to call it once.
But that's irrelevant as far as addressing goes - on x86-64 the registers are 64-bit but so are the pointers, so it's still going to take one instruction address a location in memory. Likewise, in x86 the registers are 32-bit and so are the pointers, so it's still going to take a single instruction.my thoughts exactly.
8 x16 bit commands 4 x32 bit commands 2 x64 bit commands and 1 x128 bit command all move the same data.
Should've probably clarified, I meant x86 CPUs in 32-bit mode. But yea, practical does indeed sound a bit nicer than theoretical in the context...I would call it a practical maximum. It is the way PAE is implemeneted that limits it to 64 GB. Modern 64bit CPUs have a much higher limitation.