[petsc-users] A bad commit affects MOOSE

[Derek Gaston]

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?

Derek

On Tue, Apr 3, 2018 at 11:59 AM Satish Balay <balay at mcs.anl.gov> wrote:

> On Tue, 3 Apr 2018, Smith, Barry F. wrote:
>
> >    Note that PETSc does one MPI_Comm_dup() for each hypre matrix.
> Internally hypre does at least one MPI_Comm_create() per hypre boomerAMG
> solver. So even if PETSc does not do the MPI_Comm_dup() you will still be
> limited due to hypre's MPI_Comm_create.
> >
> >     I will compose an email to hypre cc:ing everyone to get information
> from them.
>
> Actually I don't see any calls to MPI_Comm_dup() in hypre sources [there
> are stubs for it for non-mpi build]
>
> There was that call to MPI_Comm_create() in the stack trace [via
> hypre_BoomerAMGSetup]
>
> Satish
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20180403/32cc19e2/attachment.html>