From 1b72e11d72feb5e819190333db195760ac2fe1c8 Mon Sep 17 00:00:00 2001 From: Artem Zhmurov Date: Mon, 30 Dec 2019 23:20:46 +0100 Subject: [PATCH] Add description of GMX_FORCE_UPDATE_DEFAULT_GPU dev flag to the UG Refs. #3021 Change-Id: Idff63154c5ebb0b5bd209ce6025934db3aedf8fd --- docs/user-guide/environment-variables.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/user-guide/environment-variables.rst b/docs/user-guide/environment-variables.rst index 3d078d7da7..6e4da6382e 100644 --- a/docs/user-guide/environment-variables.rst +++ b/docs/user-guide/environment-variables.rst @@ -230,6 +230,14 @@ Performance and Run Control ``GMX_FORCE_UPDATE`` update forces when invoking ``mdrun -rerun``. +``GMX_FORCE_UPDATE_DEFAULT_GPU`` + Force update to run on the GPU by default, overriding the ``mdrun -update auto`` option. Works similar to setting + ``mdrun -update gpu``, but (1) falls back to the CPU code-path, if set with input that is not supported and + (2) can be used to run update on GPUs in multi-rank cases. The latter case should be + considered experimental since it lacks substantial testing. Also, GPU update is only supported with the GPU direct + communications and ``GMX_FORCE_UPDATE_DEFAULT_GPU`` variable should be set simultaneously with ``GMX_GPU_DD_COMMS`` + and ``GMX_GPU_PME_PP_COMMS`` environment variables in multi-rank case. Does not override ``mdrun -update cpu``. + ``GMX_GPU_ID`` set in the same way as ``mdrun -gpu_id``, ``GMX_GPU_ID`` allows the user to specify different GPU IDs for different ranks, which can be useful for selecting different -- 2.22.0