itaps-parallel Revised DraftInterface.h

[Onkar Sahni]

I have a question too on COPY, what will COPY mean in send/receive ent.
arr.? I think COPY in send/receive is used in different context (for
inter-part boundary entities with multiple copies imply remote-copies and
an assigned owner/supervisor among these remote-copies).

One thing I can think of in send/receive is COPY (or may be MOVE)
partition-objects from a local part to another local part.

- Onkar

> Parallel Subcommittee,
>
> Given the other functions with Copy/Copies and Owned in their names, I
> am wondering if the COPY option in the communication functions
> (sendEntArrToPartsPar/recvEntArrFromPartsPar) is redundant.  Also,
> MIGRATE will have consequences for copies.  These seem like timely
> topics given the recent discussion on the definition for neighbors.
>
> Vitus
>
> On Mon, 2008-02-11 at 14:26 -0700, Devine, Karen D wrote:
>> Attached is a revised version of DraftInterface.h, along with the CVS
>> diff
>> from the previous version you saw.
>>
>> In going through everyone's reviews, I saw that confusion remains
>> regarding
>> copies and their management.  In this week's phone conf, we'll discuss
>> the
>> communication functions (sendEntArrToPartsPar/recvEntArrFromPartsPar) as
>> well as any function with Copy/Copies and Owned in its name.
>>
>> There are many other parts of the interface marked "TODO".  Let's
>> discuss
>> them over email to reach consensus on as many as possible before using
>> phone
>> time for them.
>>
>> I have not received the new part-neighbor definition yet, so the old one
>> is
>> still in the document.
>>
>> Finally, I tried to address all comments in the reviews, but if there is
>> a
>> point that I missed or didn't address to your satisfaction, please let
>> me
>> know.
>>
>> Thanks for your contributions!
>> Karen
>>
>
>
>