My new PC mewee!:P

D

Darko

Well-known member
lol, i have 6gb ram and i am really happy with my pc's performance. got 7.8 of 7.9 rate from windows exp index:p
so installin 128 bit windows wont affect ram.
I guess there is something else!
 
Phoenix

Phoenix

Prolific Poster
What I mean is that 192 GB is the maximum amount of memory windows 7 (64-bit professional, enterprise and ultimate) can support, with the next incarnation of windows in 128-bit that limit will be extended.
 
Phoenix

Phoenix

Prolific Poster
Yeah I can't imagine any application(s) that would need anywhere near that amount, I've seen supercomputers which use 18GB of RAM and they don't seem to struggle.
 
Gorman

Gorman

Author Level
x86 / x64 and 128bit windows, the subject is a lot wider than simply being able to use more ram.

Here are some of the differences when Windows went from x86 to x64, the same sort of thing would apply to 128.

x86-64 is an extension of the x86 instruction set. It supports vastly larger virtual and physical address spaces than are possible on x86, thereby allowing programmers to conveniently work with much larger data sets.

x86-64 also provides 64-bit general purpose registers and numerous other enhancements. The original specification was created by AMD, and has been implemented by AMD, Intel, VIA, and others. It is fully backwards compatible with 32-bit code.

[1](p13) Because the full 32-bit instruction set remains implemented in hardware without any intervening emulation, existing 32-bit x86 executables run with no compatibility or performance penalties,[2] although existing applications that are recoded to take advantage of new features of the processor design may see significant performance increases.
Click to expand...

x86-64 editions of Microsoft Windows client and server, Windows XP Professional x64 Edition and Windows Server 2003 x64 Edition were released in March 2005. Internally they are actually the same build (5.2.3790.1830 SP1), as they share the same source base and operating system binaries, so even system updates are released in unified packages, much in the manner as Windows 2000 Professional and Server editions for x86.

Windows Vista, which also has many different editions, was released in January 2007. Windows Server 2008 R2 and later versions will only available as x86-64 versions. Windows for x86-64 has the following characteristics:

  • 8 TB of "user mode" virtual address space per process. A 64-bit program can use all of this, subject of course to backing store limits on the system, and provided it is linked with the "large address aware" option.[33] This is a 4096-fold increase over the default 2 GB user-mode virtual address space offered by 32-bit Windows.[34][35]
  • 8 TB of kernel mode virtual address space for the operating system.[34] As with the user mode address space, this is a 4096-fold increase over 32-bit Windows versions. The increased space is primarily of benefit to the file system cache and kernel mode "heaps" (non-paged pool and paged pool). Windows only uses a total of 16 TB out of the 256 TB implemented by the processors because early AMD64 processors lacked a CMPXCHG16B instruction.[36]
  • Ability to run existing 32-bit applications (.exe's) and dynamic link libraries (.dll's). Furthermore, a 32-bit program, if it was linked with the "large address aware" option,[33] can use up to 4 GB of virtual address space in 64-bit Windows, instead of the default 2 GB (optional 3 GB with /3GB boot option and "large address aware" link option) offered by 32-bit Windows.[37] Unlike the use of the /3GB boot option on x86, this does not reduce the kernel mode virtual address space available to the operating system. 32-bit applications can therefore benefit from running on x64 Windows even if they are not recompiled for x86-64.
  • Both 32- and 64-bit applications, if not linked with "large address aware," are limited to 2 GB of virtual address space.
  • Ability to use up to 128 GB (Windows XP/Vista), 192 GB (Windows 7), 1 TB (Windows Server 2003), or 2 TB (Windows Server 2008) of random access memory (RAM).
  • LLP64 data model: "int" and "long" types are 32 bits wide, long long is 64 bits, while pointers and types derived from pointers are 64 bits wide.
  • Kernel mode device drivers must be 64-bit versions; there is no way to run 32-bit kernel-mode executables within the 64-bit operating system. User mode device drivers can be either 32-bit or 64-bit.
  • 16-bit Windows (Win16) and DOS applications will not run on x86-64 versions of Windows due to removal of virtual DOS machine subsystem (NTVDM).
  • Full implementation of the NX (No Execute) page protection feature. This is also implemented on recent 32-bit versions of Windows when they are started in PAE mode.
  • Instead of FS segment descriptor on x86 versions of the Windows NT family, GS segment descriptor is used to point to two operating system defined structures: Thread Information Block (NT_TIB) in user mode and Processor Control Region (KPCR) in kernel mode. Thus, for example, in user mode GS:0 is the address of the first member of the Thread Information Block. Maintaining this convention made the x86-64 port easier, but required AMD to retain the function of the FS and GS segments in long mode — even though segmented addressing per se is not really used by any modern operating system.[38]
  • Early reports claimed that the operating system scheduler would not save and restore the x87 FPU machine state across thread context switches. Observed behavior shows that this is not the case: the x87 state is saved and restored, except for kernel-mode-only threads (a limitation that exists in the 32-bit version as well). The most recent documentation available from Microsoft states that the x87/MMX/3DNow! instructions may be used in long mode, but that they are deprecated and may cause compatibility problems in the future.[37]
  • Some components like Microsoft Jet Database Engine and Data Access Objects will not be ported to 64-bit architectures such as x86-64 and IA-64.[39][40]
  • Microsoft Visual Studio can compile native applications to target only the x86-64 architecture, that will run only on 64-bit Microsoft Windows, or the x86 architecture which will run as a 32-bit application on 32-bit Microsoft Windows or 64-bit Microsoft Windows in WoW64 emulation mode. Managed applications can be compiled either in x86, x86-64 or AnyCPU modes. While the first two modes behave like their x86 or x86-64 native code counterparts respectively, when using the AnyCPU mode, the applications runs as a 32-bit application in 32-bit Microsoft Windows or as a 64-bit application in 64-bit Microsoft Windows.
Click to expand...

http://en.wikipedia.org/wiki/X86-64
 
You must log in or register to reply here.
Top