Due to bug in OpenBLAS remove thread binding from defaults

The bug OpenMathLib/OpenBLAS#2238 is fixed in the
development version

Author: jussienko

docs/computing/running/creating-job-scripts-mahti.md

@@ -96,9 +96,9 @@ export OMP_NUM_THREADS=1
 srun myprog -i input -o output
 ```
 
-For hybrid applications, one should use `OMP_PLACES` and
-`OMP_PROC_BIND` OpenMP runtime environment variables for obtaining
-optimum placement of OpenMP threads. As an example, in order to run
+For hybrid applications, one should use 
+`OMP_PROC_BIND` OpenMP runtime environment variable for 
+laceming the OpenMP threads. As an example, in order to run
 one MPI tasks per NUMA domain and one OpenMP thread per L3cache one
 can set
 
@@ -107,7 +107,6 @@ can set
 #SBATCH --cpus-per-task=16
 
 export OMP_NUM_THREADS=4
-export OMP_PLACES=cores
 export OMP_PROC_BIND=spread
 
 module load myprog/1.2.3

docs/computing/running/example-job-scripts-mahti.md

@@ -52,8 +52,6 @@ srun myprog <options>
 
 # Set the number of threads based on --cpus-per-task
 export OMP_NUM_THREADS=$SLURM_CPUS_PER_TASK
-# Bind OpenMP threads to cores
-export OMP_PLACES=cores
 
 srun myprog <options>
 ```
@@ -75,8 +73,6 @@ srun myprog <options>
 
 # Set the number of threads based on --cpus-per-task
 export OMP_NUM_THREADS=$SLURM_CPUS_PER_TASK
-# Bind OpenMP threads to hardware threads
-export OMP_PLACES=threads
 
 srun myprog <options>
 ```

docs/computing/running/performance-checklist.md

@@ -54,7 +54,10 @@ higher and poor load balancing gets more likely.
 
 Many HPC applications benefit from binding OpenMP threads to CPU cores
 which can be achieved by setting `export OMP_PLACES=cores` in the
-batch job script. When starting new production runs it is also good
+batch job script. Note! Due to bug in OpenBLAS thread binding should not be
+specified when using threaded OpenBLAS (-omp module). 
+
+When starting new production runs it is also good
 practice to ensure correct thread affinity by adding to batch job
 script
 ```