Re: AWE - Shared Memory
- From: "Sudeesh" <gsudeesh@xxxxxxxxx>
- Date: 28 Aug 2006 00:08:41 -0700
Hi Arcady,
Thanx for your response and sorry for my delay. I need it for
interprocess communication. That means I cannot use AWE. I appreciate
your help.
Sudessh G
soviet_bloke@xxxxxxxxxxx wrote:
Hi Arcady
In fact, I think the OP was very precise - he asked whether he can
treat AWE memory as shared one. But in any case, you cannot really use
it the way you want - AWE imposes few limitations that memory,
allocated with VirtualAlloc(), is not subjected to
Anton Bassov
Arkady Frenkel wrote:
Only Sudeesh can say, if he wanted that for interprocess communications,
that not directly written. My point was how to work with it in that app
Arkady
<soviet_bloke@xxxxxxxxxxx> wrote in message
news:1154312711.271904.260400@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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
.
- References:
- AWE - Shared Memory
- From: Sudeesh
- Re: AWE - Shared Memory
- From: Arkady Frenkel
- Re: AWE - Shared Memory
- From: soviet_bloke
- Re: AWE - Shared Memory
- From: Arkady Frenkel
- Re: AWE - Shared Memory
- From: soviet_bloke
- AWE - Shared Memory
- Prev by Date: Avg. Disk Queue Length
- Next by Date: Re: Corruption while using asynchronous callbacks on read/write socket calls.
- Previous by thread: Re: AWE - Shared Memory
- Next by thread: RE: InitializeSecurityContext() and Digest authentication in C++
- Index(es):
Relevant Pages
|
