[petsc-users] Regarding the status of VecSetValues(Blocked) for GPU vectors
Jed Brown
jed at jedbrown.org
Thu Mar 17 16:43:57 CDT 2022
The question is about vectors. I think it will work, but haven't tested.
Barry Smith <bsmith at petsc.dev> writes:
> We seem to be emphasizing using MatSetValuesCOO() for GPUs (can also be for CPUs); in the main branch you can find a simple example in src/mat/tutorials/ex18.c which demonstrates its use.
>
> Barry
>
>
>> On Mar 17, 2022, at 4:46 PM, Sajid Ali Syed <sasyed at fnal.gov> wrote:
>>
>> Hi PETSc-developers,
>>
>> Is it possible to use VecSetValues with distributed-memory CUDA & Kokkos vectors from the device, i.e. can I call VecSetValues with GPU memory pointers and expect PETSc to figure out how to stash on the device it until I call VecAssemblyBegin (at which point PETSc could use GPU-aware MPI to populate off-process values) ?
>>
>> If this is not currently supported, is supporting this on the roadmap? Thanks in advance!
>>
>> Thank You,
>> Sajid Ali (he/him) | Research Associate
>> Scientific Computing Division
>> Fermi National Accelerator Laboratory
>> s-sajid-ali.github.io <http://s-sajid-ali.github.io/>
More information about the petsc-users
mailing list