itaps-parallel removal of

[Vitus Leung]

On Wed, 2008-03-19 at 12:43 -0600, Onkar Sahni wrote:
> > On Wed, 2008-03-19 at 10:24 -0600, Onkar Sahni wrote:
> >> >
> >> > In the specific case of repartitioning, it knows because every entity
> >> > comes to it with a part handle attached.
> >>
> >>   every local entity comes with local part-handle(s) (may be neighbors
> >> touching each other for graph-edges crossing inter-part/process bdry.)
> >> and how can a partitioning service then get local part-handle(s)
> >> transported to remote parts/processes. This is exactly the point I was
> >> trying to make during boot-camp.
> >
> > I too have been concerned about this, but had reached a conclusion
> > similar to Carl's that non-iMeshP communications would be necessary to
> > obtain remote part handles.  An iMeshP solution that removes that would
> > be fine with me.
> 
>   For non-iMeshP communications, service/user/application/client would
> have to know how to send/recv. (pack/unpack) part-handles. If we use
> integers (or pre-defined fixed number of bits) for remote part IDs it
> would be fine in case of non-iMeshP communications otherwise we may want
> to add some functionality (on this issue for part IDs) in interface.
> 
> - Onkar

Good point.

Vitus