1. 30 Oct, 2019 1 commit
  2. 28 Oct, 2019 1 commit
    • 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
      * modifying REAL_GPU_KERNEL_ONLY_WHEN_GPU_IS_ACTIVE and
        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
        begining.
      ec5b3bec
  3. 23 Oct, 2019 1 commit
  4. 22 Oct, 2019 2 commits
  5. 11 Oct, 2019 3 commits
  6. 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_
      supported.
      
      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
      dd47b584
  7. 09 Oct, 2019 10 commits
  8. 08 Oct, 2019 4 commits
  9. 07 Oct, 2019 2 commits
  10. 01 Oct, 2019 1 commit
  11. 30 Sep, 2019 1 commit
  12. 26 Sep, 2019 4 commits
  13. 24 Sep, 2019 1 commit
  14. 23 Sep, 2019 2 commits
  15. 20 Sep, 2019 1 commit
  16. 12 Sep, 2019 1 commit
  17. 11 Sep, 2019 1 commit
  18. 09 Sep, 2019 1 commit
  19. 06 Sep, 2019 1 commit
  20. 05 Sep, 2019 1 commit