[Mpi3-hybridpm] Hybrid WG meeting at the Forum
Douglas Miller
dougmill at us.ibm.com
Tue Dec 7 07:58:25 CST 2010
In order to ensure all nodes get the same memory segment, they all have to
use the same "key". At least if this is implemented on Unix SysV or POSIX
shmem. Then there's the possibility of some nodes allocing on a sub-comm
first, etc. I think its just avoiding a lot of potential complications and
don't see what the downside is.
_______________________________________________
Douglas Miller BlueGene Messaging Development
IBM Corp., Rochester, MN USA Bldg 030-2 A410
dougmill at us.ibm.com Douglas Miller/Rochester/IBM
"Ron Brightwell"
<rbbrigh at sandia.g
ov> To
Sent by: "mpi3-hybridpm at lists.mpi-forum.org"
mpi3-hybridpm-bou <mpi3-hybridpm at lists.mpi-forum.org>
nces at lists.mpi-fo cc
rum.org
Subject
Re: [Mpi3-hybridpm] Hybrid WG
12/07/2010 12:11 meeting at the Forum
AM
Please respond to
mpi3-hybridpm at lis
ts.mpi-forum.org
On 12/06/2010 05:59 PM, James Dinan wrote:
> On 12/6/10 5:49 PM, Pavan Balaji wrote:
>> Hi Doug,
>>
>> On 12/06/2010 11:42 AM, Douglas Miller wrote:
>>> Re: SHMEM ALLOC: I thought we were considering adding a "const char
>>> *key" param so that shared memory allocations better match OS (e.g.
>>> POSIX) shmem allocations and also to allow the call to be
>>> non-synchronizing.
>>
>> As I recalled, this was still being discussed. Did we decide on adding
>> the key? Ron?
>>
>> I'll add it in as a discussion item.
>
> I think that the key is primarily helpful as a bootstrap mechanism for
> processes to ensure they connect to the right shared segment. I think
> the intent was to have shmem alloc be collective so this should be
> extraneous.
Right. I think you lose several important optimizations for shared
memory if the call is not collective. It doesn't have to be synchronous,
but it does have to be collective.
-Ron
_______________________________________________
Mpi3-hybridpm mailing list
Mpi3-hybridpm at lists.mpi-forum.org
http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-hybridpm
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpi-forum.org/pipermail/mpiwg-hybridpm/attachments/20101207/5b77ba76/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://lists.mpi-forum.org/pipermail/mpiwg-hybridpm/attachments/20101207/5b77ba76/attachment-0003.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic08883.gif
Type: image/gif
Size: 1255 bytes
Desc: not available
URL: <http://lists.mpi-forum.org/pipermail/mpiwg-hybridpm/attachments/20101207/5b77ba76/attachment-0004.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ecblank.gif
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://lists.mpi-forum.org/pipermail/mpiwg-hybridpm/attachments/20101207/5b77ba76/attachment-0005.gif>
More information about the mpiwg-hybridpm
mailing list