MAGMA Forum

Let me see if I understand you correctly. MAGMA doesn't have any MPI. So you are calling MAGMA for node-local computations on each node, and you are doing your own MPI communication. And in this context, MAGMA running in one MPI rank is giving the wrong result. Right? CUDA counts GPUs from 0. You ca...

This is a known issue with CMake on Windows (see issue below). We have not yet found a feasible work around.
https://gitlab.kitware.com/cmake/cmake/ ... ote_642545

Mark

Can you give more specifics such as: version of MAGMA (e.g., MAGMA 2.5.2) C/C++ compiler & version (e.g., g++ 9.2.0) CUDA version (e.g., CUDA 10.0) Is this an error compiling MAGMA, or an error compiling your application using MAGMA? If it's your application, please include a minimum code example th...

Are you using MAGMA's testers to test these, e.g., testing/testing_zheevd? Which specific routine are you using? If using MAGMA's tester, can you share the complete input & output that is concerning you? We generally check the relative backwards error, || A - U S U^H ||_1 / ( || A ||_1 N ) MAGMA's t...

Thanks for your input. We'll keep it in mind for future developments.
-mark

SLATE is a good choice for a distributed solver with CPUs or CPUs + GPUs. For using CPUs + GPUs, it would require that the distributed matrix fits in the cumulative memory of all the GPUs. For a single node, MAGMA will also do out-of-GPU-memory algorithms for such large matrices. Just call magma_dge...

You can name mangle the functions in magma/testing/lin/
In magma/testing/Makefile.sr, see variable liblapacktest_src for the 36 or so files that are used. The other files in that directory were copied from LAPACK but aren't used.

-mark

[sdcz]qpt01 are LAPACK testing functions. They would not be in the LAPACK library, per se, but in LAPACK's testing. MAGMA has its own copy of them: >> pfind -i qpt01 lapack lapack/TESTING/LIN/cqpt01.f lapack/TESTING/LIN/dqpt01.f lapack/TESTING/LIN/sqpt01.f lapack/TESTING/LIN/zqpt01.f >> pfind -i qpt...

magma_cgesv works on multiple GPUs; it calls magma_cgetrf, which calls magma_cgetrf_m. However, as you observe, the forward and back solves (getrs) are on the CPU. It's unclear if multi-GPU pivoting (laswp) and triangular solves (trsm) in getrs would benefit from the GPU, since there would be signif...

Yes, magma_dmalloc is just a wrapper around cudaMalloc. It is type-safe (you don't need to use sizeof(double) as you do with cudaMalloc), but otherwise nothing special going on. If you call asynchronous MAGMA routines that take a magma_queue, use the stream from the magma_queue to call CUDA function...