itaps-parallel iMeshP_syncPartitionAll, iMeshP_getNumGlobalParts, and communication
Jason Kraftcheck
kraftche at cae.wisc.edu
Wed Oct 15 09:29:58 CDT 2008
Onkar Sahni wrote:
> See my comments below:
>
>> 1) Do global communication for all partitions during file load to cache
>> global number of parts for each partition read from file.
>>
>
> iMesh_load allows only one partition (i.e., iMeshP_PartitionHandle) as
> an input. So I do not know what load of 'all partitions' means... (may
> be I am missing something). And as per my understanding either
> iMesh_load is collective or is followed by call to
> iMeshP_syncPartitionAll
>
iMesh_load allows one partition to use to distribute the mesh amongst
processors (one active partition). That does not mean that there cannot be
others (e.g. doing partitioning in parallel).
>> 2) Require application to associate an an MPI_Comm with any partition (we
>> don't have an API for this) and call iMeshP_syncPartitionAll on it
>> before expecting to be able to get any global data.
>>
>
> iMeshP_createPartitionAll takes MPI_Comm as an input and as per my
> understanding thats how application will associate an MPI_Comm with any
> partition.
>
But that only works if the application creates the partition.
- jason
More information about the itaps-parallel
mailing list