Currently, all software for a given CPU microarchitecture is installed under the same EASYBUILD_INSTALLPATH. For supporting builds which include GPU-accelerated software we want to install these into sub-directories where each sub-directory contains builds that are optimized for a specific GPU (or CUDA compute capability if the software is build for NVIDIA GPUs). For example, if we want to build for CUDA compute capability 8.0 that would run on a zen3 CPUs, the standard installation path for CPU-only builds would be
We could add hooks (via eb_hooks.py) which check if a GPU-build is requested (e.g., whether a CUDA compute capability is given and if CUDA is a dependency). If so, we could change the installation path.
Currently, all software for a given CPU microarchitecture is installed under the same
EASYBUILD_INSTALLPATH
. For supporting builds which include GPU-accelerated software we want to install these into sub-directories where each sub-directory contains builds that are optimized for a specific GPU (or CUDA compute capability if the software is build for NVIDIA GPUs). For example, if we want to build for CUDA compute capability8.0
that would run on azen3
CPUs, the standard installation path for CPU-only builds would beSoftware packages that are built for CUDA compute capability
8.0
will be installed underWe could add hooks (via
eb_hooks.py
) which check if a GPU-build is requested (e.g., whether a CUDA compute capability is given and ifCUDA
is a dependency). If so, we could change the installation path.For further information, see https://github.com/EESSI/meetings/wiki/bot-sync-meeting-2024-06-14