[petsc-dev] GAMG error with MKL

[Mark Adams]

> If PETSc was an application, it could do whatever it wanted, but it's
> not.  If PETSc is a library that intends to meet the needs of HPC
> applications, it needs to support the programming models the applications
> are using.
>

To repeat, PETSc supports threads, currently with MKL kernels and third
party solvers (hypre), and GPUs with native solvers and again through
hypre. I'm sure we will add more mechanism in the future. (I really don't
know how to say this any more clearly.)


> Or I suppose you will continue to disparage everyone who doesn't bow down
> and worship flat MPI on homogeneous big-core machines as a divine execution
> model until your users abandon you for otherwise inferior software that is
> willing to embrace user requirements.
>

I agree, and I suspect we have a consensus that we should not disparage
threads publicly as much (or at all) in the future as we have. It just does
not do any good. Those that get it get it and those that don't don't.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20180710/a613c4c6/attachment.html>