Dear Inge,
On 04/04/2019 08:43, Inge Gutheil wrote:
Hi,
Damian told me that the correct avx512 flag to be checked is the
avx512f, which is
AVX512F - AVX-512 Foundation is base of the 512-bit SIMD instruction
extensions which is a comprehensive list of features for most HPC and
enterprise applications. AVX-512 Foundation is the natural extensions to
AVX/AVX2 which is extended using the EVEX prefix which builds on the
existing VEX prefix. Any processor that implements any portion of the
AVX-512 extensions MUST implement AVX512F.
according to NVIDIA.
Now I get the next problem when I want to configure ELPA for usage with
GPU acceleration. The ea runs on "normal" nodes without GPUs and I don't
know whether the auto_detect_cpu_features would detect GPUs anyway, so I
have to add the additional options --enable-gpu
--with-GPU-compute-capability="sm_70" (the capability is just an example)
Now with the new ELPA easyblock neither configopts nor common_configopts
seem to be defined, so how can I add those features?
I assume you're referring to the ELPA easyblock that is being
contributed in
https://github.com/easybuilders/easybuild-easyblocks/pull/1621 .
Note that this easyblock is not final yet, it's subject to changes.
Like the change that is required for avx512f that you ran into; can you
clarify what you had to change to make that work as expected?
What it just a matter of changing the 'avx512' to 'avx512f' in the
ELPA_CPU_FEATURE_FLAGS list?
W.r.t. adding additional configure options: the ELPA easyblock is
constructed in such a way that you can pass additional configure options
via the ELPA easyconfig file (ELPA*.eb), by including the following for
example:
configopts = '--enable-gpu --with-GPU-compute-capability="sm_70"'
You shouldn't have to change anything to the ELPA easyblock that is
proposed in
https://github.com/easybuilders/easybuild-easyblocks/pull/1621 to make
this work...
Can you give that a try, and let us know if that works as expected?
regards,
Kenneth
Regards
Inge Gutheil
