Re: [petsc-dev] model for parallel ASM

I've managed to read through your MR posts today. As I said there getting parallel fieldsplit/additive solves is what I'm after. Maybe start with Jacobi. And I am MPI serial so my scatter gathers are local in PCApply_FieldSplit. FYI, Christan Trott responded with this wrt the future Kokkos interf

Re: [petsc-dev] looking at all threads in MR after they are resolved

On Sat, 9 Jan 2021, Barry Smith wrote: > > > > On Jan 9, 2021, at 8:16 PM, Satish Balay wrote: > > > > On Sat, 9 Jan 2021, Barry Smith wrote: > > > >> > >> For unresolved threads you can press the arrow in the upper right to > >> find the next unresolved thread. > >> > >> But how do y

Re: [petsc-dev] model for parallel ASM

Hmm I suppose this means Kokkos should accept a stream like we expect it to? According to this somewhat recent merged PR: https://github.com/kokkos/kokkos/pull/1919 you can now make a "Kokkos::Cuda” object, and pass it as arg1 to range policies as an

Re: [petsc-dev] model for parallel ASM

> I could try this with fieldsplit/additive and Jacob's Vector object on Cuda, > with Jacobi now of its ready. Jacob? Still under construction, although depending on the exact vec ops you require you may be able to tinker something together. Note so far only direct vec compute ops have been giv

Re: [petsc-dev] model for parallel ASM

Jacob, I'm not sure I understand this response. I could not find you on the Kokkos slack channel. Me: And My colleague in PETSc, Jacob Faibussowitsch, has talked to you about Kokkos taking a Cuda, Hip, etc., stream. This is something that would make it easier to deal with asynchronous GPU solvers

Re: [petsc-dev] model for parallel ASM

Ah, so first first maybe the Solver does not need a stream because it uses VecScatter ? The model is 1) block to get your data, 2) doit non-blocking. If a vector is used in a non-GPU method that does not know about (1) you are hosed, but that is a detail. I like the middle, single loop algo or wh