1. 11 Nov, 2019 1 commit
  2. 08 Nov, 2019 1 commit
  3. 05 Nov, 2019 1 commit
  4. 04 Nov, 2019 2 commits
  5. 31 Oct, 2019 1 commit
  6. 30 Oct, 2019 3 commits
  7. 29 Oct, 2019 1 commit
  8. 28 Oct, 2019 2 commits
    • Andreas Marek's avatar
      Merge branch 'master_pre_stage' into skew · cfa307bb
      Andreas Marek authored
    • Pavel Kus's avatar
      partially addressing issues with the GPU kernel · ec5b3bec
      Pavel Kus authored
      This commit addresses several issues. It essentially forbids the use of
      the GPU kernel, which become obsolete and caused problems. But it
      does not complete remove the related code, nor does it forbid from
      explicitly selecting the GPU kernel. However, if the user does select
      it, the warning will be issued and the GENERIC kernel would be used
      instead. In the more details:
      * Commentin out operations in the GPU kernel, which do not compile with
        CUDA 10.1. This makes the kernel deffinitely not ussable (but it was
        true even before)
      * removing the gpu_tridiag_band option, sincie the tridiag->banded routine
        is actually not ported to GPU at all. This step will thus always be
        run on the CPU
      * removing the gpu_trans_ev_tridi_to_band option, since the GPU version
        of this step cannot run without the GPU kernel and it is not usable.
        This step will thus also be performed on the CPU
        COMPLEX_GPU_KERNEL_ONLY_WHEN_GPU_IS_ACTIVE such that the GPU kernel is
        not considered during the autotuning
      * TODO however, the GPU kernel can still be enforced by the user. In
        this case, during the calculation, a warning is issued and the kernel
        is switched to the GENERIC one. This should be improved and there
        should not even be the possibility to choose the GPU kernel at the
  9. 26 Oct, 2019 2 commits
  10. 25 Oct, 2019 1 commit
  11. 24 Oct, 2019 7 commits
  12. 23 Oct, 2019 3 commits
  13. 22 Oct, 2019 3 commits
    • Pavel Kus's avatar
      fixing not freed a_dev · 57821b44
      Pavel Kus authored
      a_dev was never freed on the GPU
      However, this might not be enough. What if bandred runs on GPU and
      band_to_tridi on CPU? a_dev is then not allocated. Has to be re-thinked
      in general
    • Sebastian Ohlmann's avatar
      Add support for NVTX profiling · bf7c6410
      Sebastian Ohlmann authored
      When profiling the GPU version, NVTX can be used to highlight the
      corresponding regions of the code in the timeline of the profiling tool
      (nvvp or nsight systems). This is very useful to correlate what happens
      on the GPU with what part of the code we are in.
    • Pavel Kus's avatar
      adding tool to check GPU memory · 82ffbd38
      Pavel Kus authored
  14. 21 Oct, 2019 1 commit
  15. 19 Oct, 2019 2 commits
  16. 17 Oct, 2019 2 commits
  17. 14 Oct, 2019 1 commit
    • Andreas Marek's avatar
      Enable 64bit lapack support · d836eea2
      Andreas Marek authored
      ELPA can now link agains a 64bit integer verion of BLAS/LAPACK.
      Currently this only works if ELPA is compiled with MPI=OFF!
      The 64bit support is not available in the legacy interface
  18. 11 Oct, 2019 5 commits
  19. 10 Oct, 2019 1 commit
    • Andreas Marek's avatar
      HETEROGENOUS_CLUSTER support · dd47b584
      Andreas Marek authored
      On heterogenous cluster, of nodes with different CPUs the _experimental_
      feature (--enable-heterogenous-cluster-support) can be used:
      It compares the (Intel) cpuid set of all CPUs which are used by ELPA MPI
      processes and finds the SIMD instruction set, which is supported by all
      used CPUs. The ELPA 2stage back-transformation kernel (a.k.a "kernel")
      will be set accordingly on all MPI processes.
      This feature, can override the setting of the kernel done previously by
      the user!
      At the moment it will only work for Intel CPUs, i.e. clusters consisting
      of nodes with Intel CPUs and e.g. AMD CPUs are at the moment _NOT_
      Since this is an experimental feature, it might be dropped again in the
      future, if it turns out not to be useful for the users