itaps-parallel Notes from 3/3/08 phone conference

[txie at scorec.rpi.edu]

Hi All,

The attached is our proposed non-collective migration functions based on
the 5 needs from Karen's last email. Currently, we have some questions
about the 5 functions listed below (I also put them in the attached file).
Please let us know if you have any problems. Thanks.

Regards,

Ting

------------------------------------------------------

First, do we need functions of array versions for Need 1, 2 and 5?

>
> Non-collective communication needed:
> 1.  Requests to migrate remote entities and (optionally) their
> higher-order
> adjacencies.  Note that the iMesh implementation must be smart enough to
> change ownership of lower-order entities that become orphaned due to
> migration.
------------------------------------------------------
We don't use argument include_upward_adj, because we think that we only
migrate all (partition) objects around the lower-order mesh entity that is
on the part boundary.

> 2.  Push entity data from owner to other parts for migrating entities and
> updating remote copies.
------------------------------------------------------
Here, the term 'remote copies' can be modified to 'ghost entities'.

> 5.  Capability to replace an entity with new entities, both locally and
> remotely.  This capability would include requests to perform an operation
> on
> an entity copy (e.g., split that edge), as well as communication to update
> remote entity handles for the new entities created.
------------------------------------------------------
Do we need to specify an argument 'int Replace_OP' in this function?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: migration_interface.h
Type: application/octet-stream
Size: 3751 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/itaps-parallel/attachments/20080306/c9bdb05e/attachment.obj>