Re: [petsc-dev] Kokkos error on SUMMIT
On Fri, Oct 2, 2020 at 3:02 PM Junchao Zhang wrote: > > > On Fri, Oct 2, 2020 at 2:59 PM Mark Adams wrote: > >> >> >> On Fri, Oct 2, 2020 at 3:15 PM Barry Smith wrote: >> >>> >>> Mark, >>> >>> Looks like you are building Kokkos without CUDA. >> >> >> Yes. This is a CPU build of Kokkos. >> >> >>> You don't have --with-cuda on configure line that is used by Kokkos to >>> determine what version to build. >>> >>> Junchao, >>> >>> I guess you need to test Kokkos Kernels without CUDA and HIP and make >>> a few changes. >>> >> >> I'm trying with OpenMP right now. If you want CPU runs then asking for >> OMP is not terrible. >> >> > That is an interesting feature of Kokkos. > By the design, even 'device' memory is now the host memory. The computation is still diverted to Kokkos backend. In other words, petsc supports multithreading through Kokkos. > > >> >>> Barry >>> >>> >>> >>> >>> #if defined(PETSC_HAVE_CUDA) >>> #define WaitForKokkos() PetscCUDASynchronize ? (Kokkos::fence(),0) : 0; >>> #elif defined(PETSC_HAVE_HIP) >>> #define WaitForKokkos() PetscHIPSynchronize ? (Kokkos::fence(),0) : 0; >>> #endif >>> >>> >>> >>> > On Oct 2, 2020, at 11:47 AM, Mark Adams wrote: >>> > >>> > >>> > >>> >>>
Re: [petsc-dev] Kokkos error on SUMMIT
On Fri, Oct 2, 2020 at 2:59 PM Mark Adams wrote: > > > On Fri, Oct 2, 2020 at 3:15 PM Barry Smith wrote: > >> >> Mark, >> >> Looks like you are building Kokkos without CUDA. > > > Yes. This is a CPU build of Kokkos. > > >> You don't have --with-cuda on configure line that is used by Kokkos to >> determine what version to build. >> >> Junchao, >> >> I guess you need to test Kokkos Kernels without CUDA and HIP and make a >> few changes. >> > > I'm trying with OpenMP right now. If you want CPU runs then asking for OMP > is not terrible. > > That is an interesting feature of Kokkos. > >> Barry >> >> >> >> >> #if defined(PETSC_HAVE_CUDA) >> #define WaitForKokkos() PetscCUDASynchronize ? (Kokkos::fence(),0) : 0; >> #elif defined(PETSC_HAVE_HIP) >> #define WaitForKokkos() PetscHIPSynchronize ? (Kokkos::fence(),0) : 0; >> #endif >> >> >> >> > On Oct 2, 2020, at 11:47 AM, Mark Adams wrote: >> > >> > >> > >> >>
Re: [petsc-dev] Kokkos error on SUMMIT
On Fri, Oct 2, 2020 at 3:15 PM Barry Smith wrote: > > Mark, > > Looks like you are building Kokkos without CUDA. Yes. This is a CPU build of Kokkos. > You don't have --with-cuda on configure line that is used by Kokkos to > determine what version to build. > > Junchao, > > I guess you need to test Kokkos Kernels without CUDA and HIP and make a > few changes. > I'm trying with OpenMP right now. If you want CPU runs then asking for OMP is not terrible. > > Barry > > > > > #if defined(PETSC_HAVE_CUDA) > #define WaitForKokkos() PetscCUDASynchronize ? (Kokkos::fence(),0) : 0; > #elif defined(PETSC_HAVE_HIP) > #define WaitForKokkos() PetscHIPSynchronize ? (Kokkos::fence(),0) : 0; > #endif > > > > > On Oct 2, 2020, at 11:47 AM, Mark Adams wrote: > > > > > > > >
Re: [petsc-dev] Kokkos error on SUMMIT
Mark, Looks like you are building Kokkos without CUDA.You don't have --with-cuda on configure line that is used by Kokkos to determine what version to build. Junchao, I guess you need to test Kokkos Kernels without CUDA and HIP and make a few changes. Barry #if defined(PETSC_HAVE_CUDA) #define WaitForKokkos() PetscCUDASynchronize ? (Kokkos::fence(),0) : 0; #elif defined(PETSC_HAVE_HIP) #define WaitForKokkos() PetscHIPSynchronize ? (Kokkos::fence(),0) : 0; #endif > On Oct 2, 2020, at 11:47 AM, Mark Adams wrote: > > >
[petsc-dev] Kokkos error on SUMMIT
configure.log Description: Binary data make.log Description: Binary data
[petsc-dev] pull request tutorial October 15 at 2pm central
Hi, Thank you to Patrick for giving his tutorial on sphinx. The slides should soon be available at: https://docs.petsc.org/en/latest/developers/documentation/#sphinx-documentation Our next tutorial will be October 15 at 2pm central. Barry will be leading a tutorial on pull requests from preparing the request to what happens during the review and after the pull request is accepted. Please email Barry directly if you have questions that you would like him to address in the tutorial. The information for the call is below. Thanks, Todd. To join the meeting on a computer or mobile phone: https://bluejeans.com/753281003?src=calendarLink Phone Dial-in +1.312.216.0325 (US (Chicago)) +1.408.740.7256 (US (San Jose)) +1.866.226.4650 (US Toll Free) Global Numbers: https://www.bluejeans.com/premium-numbers Meeting ID: 753 281 003 Room System 199.48.152.152 or bjn.vc Meeting ID: 753 281 003 Want to test your video connection? https://bluejeans.com/111
