Re: Windows array allocation problem
- From: glen herrmannsfeldt <gah@xxxxxxxxxxxxxxxx>
- Date: Sat, 29 Sep 2007 17:33:01 -0800
Roy Lewallen wrote:
(snip)
As I understand Windows operation, each Windows application has its own 2 GB of addressable virtual memory space. The total virtual memory available to all running applications can add up to a great deal more than 4 GB. This is swapped to and from actual memory and the disk as needed.
On a 32 bit system you have 4GB of virtual address space. The way many
systems (including windows) use that space is 2GB for the system, common
among all programs and 2GB private space for each program. The total
virtual memory may be greater than 4GB, but only 4GB is addressable
at one time.
I have seen systems with more than 2GB of available swap space,
and programs that determine the available memory find a negative
number (treating it as a signed 32 bit value) deciding that not
enough is available. I have seen the same thing for available
disk space.
-- glen
.
- References:
- Windows array allocation problem
- From: Roy Lewallen
- Re: Windows array allocation problem
- From: glen herrmannsfeldt
- Re: Windows array allocation problem
- From: Roy Lewallen
- Windows array allocation problem
- Prev by Date: Re: Windows array allocation problem
- Next by Date: Re: Windows array allocation problem
- Previous by thread: Re: Windows array allocation problem
- Next by thread: Re: Windows array allocation problem
- Index(es):
Relevant Pages
|