Max process size

Do you confirm max size for any (user) process under Windows CE 4.20 and
Windows CE 5.0 is 32 Mb?

Max

Sue
Wed May 17 10:32:50 CDT 2006

In Windows CE 5.0, every process gets a maximum of 32MB of virtual memory.
For more information on that, please see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dncenet/html/advmemmgmt.asp

BTW in Windows CE 6 beta, every process gets 2GB of virtual memory.

Sue
sloh@microsoft.com (remove "online" from reply-to address)
http://blogs.msdn.com/ce_base/
_____________________________________________________________
This posting is provided "AS IS" with no warranties, and confers no rights.
_____________________________________________________________

Dean
Tue May 23 09:19:37 CDT 2006

Note that doesn't necessarily mean you can't access memory in amounts larger
than 32MB...

--
Dean Ramsier - eMVP
BSQUARE Corporation


"Sue Loh [MS]" <sloh@online.microsoft.com> wrote in message
news:O8rhpcceGHA.4276@TK2MSFTNGP03.phx.gbl...
> In Windows CE 5.0, every process gets a maximum of 32MB of virtual memory.
> For more information on that, please see
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dncenet/html/advmemmgmt.asp
>
> BTW in Windows CE 6 beta, every process gets 2GB of virtual memory.
>
> Sue
> sloh@microsoft.com (remove "online" from reply-to address)
> http://blogs.msdn.com/ce_base/
> _____________________________________________________________
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> _____________________________________________________________
>
>

Mhaxx
Tue May 23 10:11:52 CDT 2006

> Note that doesn't necessarily mean you can't access memory in amounts
larger
> than 32MB...

Sure, if max process size is 32 Mb this means my application can't access an
amount of memory bigger than 32 Mb..

Max

Valter
Tue May 23 11:28:36 CDT 2006

"Mhaxx" <supermhaxx@despammed.com> wrote in
news:erwjnqnfGHA.1204@TK2MSFTNGP02.phx.gbl:

[...]
> Sure, if max process size is 32 Mb this means my application can't
> access an amount of memory bigger than 32 Mb..

No, this means that you can't map more than 32Mb inside the address
slot of your process (32Mb in size).
You can allocate up to 1Gb of shared memory (1Gb-64Mb) and every
allocation of more than 2Mb will be automatically allocated inside the
shared memory address space IIRC.
This doesn't mean that this block of memory will be accessible to any
other application. It will be private to your process unless you decide
to share it explicitly giving it a name (like it happens with mutexes
and other synchronization objects).

--
Valter Minute
(the reply address of this message is invalid)
(l'indirizzo di reply di questo messaggio non è valido)

Mhaxx
Wed May 24 02:22:45 CDT 2006

> No, this means that you can't map more than 32Mb inside the address
> slot of your process (32Mb in size).
> You can allocate up to 1Gb of shared memory (1Gb-64Mb) and every
> allocation of more than 2Mb will be automatically allocated inside the
> shared memory address space IIRC.

I can't understand the difference.. I thought to be able to allocate up to
32 Mb, not over. But you're saying it's possible.. please, try to explain to
me if my application can be more than 32 Mb of RAM and how. Thank you..

> This doesn't mean that this block of memory will be accessible to any
> other application. It will be private to your process unless you decide
> to share it explicitly giving it a name (like it happens with mutexes
> and other synchronization objects).

?

Max

Dean
Wed May 24 11:59:59 CDT 2006

The 32MB refers to memory that is dedicated to your process. There is
another large region of memory that is accessible by all processes, and is
used for memory mapped files, large virtual memory allocations etc. You can
use that shared memory if you allocate it with the memory mapped file and
VirtualAlloc apis.

Some types of memory allocations can only come from your process space.
This includes program memory, dlls, stacks etc. This is where you will hit
the 32MB limit. Your application itself can't exceed 32MB (far less than
that due to the other items that must come from this same space). But that
doesn't mean you can't access large amounts of memory.

--
Dean Ramsier - eMVP
BSQUARE Corporation


"Mhaxx" <supermhaxx@despammed.com> wrote in message
news:uHa3HJwfGHA.2172@TK2MSFTNGP04.phx.gbl...
>> No, this means that you can't map more than 32Mb inside the address
>> slot of your process (32Mb in size).
>> You can allocate up to 1Gb of shared memory (1Gb-64Mb) and every
>> allocation of more than 2Mb will be automatically allocated inside the
>> shared memory address space IIRC.
>
> I can't understand the difference.. I thought to be able to allocate up to
> 32 Mb, not over. But you're saying it's possible.. please, try to explain
> to
> me if my application can be more than 32 Mb of RAM and how. Thank you..
>
>> This doesn't mean that this block of memory will be accessible to any
>> other application. It will be private to your process unless you decide
>> to share it explicitly giving it a name (like it happens with mutexes
>> and other synchronization objects).
>
> ?
>
> Max
>
>

Mhaxx
Thu May 25 03:55:48 CDT 2006

> another large region of memory that is accessible by all processes, and is
> used for memory mapped files, large virtual memory allocations etc. You
can
> use that shared memory if you allocate it with the memory mapped file and
> VirtualAlloc apis.

That's right.

> Some types of memory allocations can only come from your process space.

Ok, thank you so much.

Max