>> That is just stupid since 32bit cannot address more >> than 4GB of memory no matter what you do. Any sysadmin should know >> that right?
>That's per process. All reasonably recent 32-bit OSs can address way >more than 4GiB internally. Yes, but one region in memory is reserved for IO. Drivers use high memory addreses (>3Gb) to speak with their devices. To support more than 3Gb on Win/32bit PAE could be used so IO would reside higher than 4Gb. But in this situation drivers need to deal with 64bit pointers. Microsoft believes it would lead to driver fails and BSODs, so it denied it for desktop versions of OSes. But it works in server versions. Idea was: "4Gb is rarely needed on desktop and desktop has cheap hardware and poorly-written drivers. And on server they have good hardware and good drivers and often require more than 4Gb." You could use +4Gb on Win2008/32bit but you _can't_ use more than about 3.5Gb on Win7@32bit. BTW process could access more than 4Gb too (see AWE: http://msdn.microsoft.com/en-us/library/windows/desktop/aa366527(v=vs.85).as px) but AFAIK Sun JVM does not use it >If you have relatively small processes, there's no need for >the overhead of 64-bit even if you have 16GiB or more. You can run 32bit apps on 64bit windows (that's called WoW64). Processor and Windows support it and it works pretty well. Ilya Kazakevich, Developer JetBrains Inc http://www.jetbrains.com "Develop with pleasure!" --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
