Stan Moore
Stan Moore
Calling `Kokkos::initialize()` after `Kokkos::finalize()` can lead memory corruption and crashes with the `Serial` backend, see https://github.com/lammps/lammps/pull/2470. Some backends like `Cuda` check for this and error out, see https://github.com/kokkos/kokkos/blob/master/core/src/Cuda/Kokkos_Cuda_Instance.cpp#L306, while others...
From mail list: It would be really handy if the fix reax/c/bonds command had the '*' option to output one file per timestep
USER-DPD fix_rx segfaults when its input file (such as kinetics.dpdrx) is invalid (for example, if there is a stray line). Ideally it should error out gracefully and notify the user...
It would be nice if there was a way to see total memory transferred between different memory spaces, specifically between GPU and CPU.
I need to run the Kokkos kernel logger on hundreds of thousands of MPI ranks for many hours to debug an issue. I only care about the last few kernels,...
On my Mac laptop, the Kokkos memory profiling values from `getrusage` are off by a factor 1024. This is because `getrusage` uses units of *bytes* on Mac but *kilobytes* on...
Should gracefully error out instead of segfaulting, and alert the user to use dynamic linking.
The HighWater-Process(MB) metric for the CUDA memory space (file *.Cuda.memspace_usage) is bogus, it is for the host and doesn't accurately reflect the CUDA value.
When there are a lot of memory events, Kokkos memory events itself can have significant memory overhead due to storing all of the events. This should be subtracted off to...
If the code crashes while profiling, like due to out of memory, there is zero output from the memory tools, which doesn't help debugging. It would be nice if the...