Sounds great to me - what library do I download that we're all going to use for managing the memory pool? :-)
Seriously though: why doesn't MPI give us an ability to get unique tag IDs for a given communicator? I like the way libMesh deals with this: https://github.com/libMesh/libmesh/blob/master/include/parallel/parallel_implementation.h#L1343 I would definitely sign on for all of us to use the same library for getting unique tag IDs... and then we would need a lot less communicators... Derek On Tue, Apr 3, 2018 at 3:20 PM Jed Brown <[email protected]> wrote: > Derek Gaston <[email protected]> writes: > > > Do you think there is any possibility of getting Hypre to use disjoint > tags > > from PETSc so you can just use the same comm? Maybe a configure option > to > > Hypre to tell it what number to start at for its tags? > > Why have malloc when we could just coordinate each of our libraries to > use non-overlapping memory segments??? >
