Re: AWE - Shared Memory
- From: soviet_bloke@xxxxxxxxxxx
- Date: 30 Jul 2006 19:25:11 -0700
Hi Arcady
I am afraid you are totally wrong. Text below is precise quotation of
MSDN:
(http://windowssdk.msdn.microsoft.com/en-us/library/ms693507.aspx)
/////////
Virtual address ranges allocated for the AWE are not sharable with
other processes (and therefore not inheritable). In fact, two different
AWE virtual addresses within the same process are not allowed to map
the same physical page. These restrictions provide fast remapping and
cleanup when memory is freed.
///////////
In fact, as long as you map less than 4G of RAM, AWE does not even
require PAE enabled. In this case you can think of memory, mapped with
MapUserPhysicalPages(), just as of constantly resident, non-sharable
and always read-write pages
Anton Bassov
Arkady Frenkel wrote:
If you mean PAE (
http://www.microsoft.com/whdc/system/platform/server/PAE/PAEdrv.mspx ) that
should be virtual for user mode apps so for sure you can use it for your
purposes
Arkady
"Sudeesh" <gsudeesh@xxxxxxxxx> wrote in message
news:1153892721.041982.11270@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello,
Can we use Address Windows Extension(AWE) for shard memory or Memory
Mapped File? If so, how can we implement?
Thank You and Best regards,
Sudeesh G
.
- Follow-Ups:
- Re: AWE - Shared Memory
- From: Arkady Frenkel
- Re: AWE - Shared Memory
- References:
- AWE - Shared Memory
- From: Sudeesh
- Re: AWE - Shared Memory
- From: Arkady Frenkel
- AWE - Shared Memory
- Prev by Date: Re: Winsock: Strange behaviour
- Next by Date: Re: RTP streaming
- Previous by thread: Re: AWE - Shared Memory
- Next by thread: Re: AWE - Shared Memory
- Index(es):
Relevant Pages
|
