[petsc-users] A bad commit affects MOOSE

Jed Brown jed at jedbrown.org
Tue Apr 3 17:28:44 CDT 2018


Matthew Knepley <knepley at gmail.com> writes:

> On Tue, Apr 3, 2018 at 6:20 PM, Jed Brown <jed at jedbrown.org> wrote:
>
>> Derek Gaston <friedmud at gmail.com> writes:
>>
>> > On Tue, Apr 3, 2018 at 4:06 PM Jed Brown <jed at jedbrown.org> wrote:
>> >
>> >> Communicators should be cheap.  One per library per "size" isn't a huge
>> >> number of communicators.
>> >>
>> >
>> > I agree - but that's not what we're getting here.  We're getting one per
>> > "object" (Mat / Preconditioner, etc.) associated with the library per
>> > "size".  If we can fix that I agree that there's no problem (we use a lot
>> > of libraries... but not 2000 separate ones simultaneously!).
>>
>> So PETSc needs to dup and attach a hypre communicator because they
>> aren't interested in doing it themselves.  Not hard to implement, just
>> mildly annoying.
>>
>
> Can't someone tell them its an xSDK requirement?

xSDX is busy with threads... ;-)


More information about the petsc-users mailing list