Skip to content
Snippets Groups Projects
Commit 63aad352 authored by sjplimp's avatar sjplimp
Browse files 

git-svn-id: svn://svn.icms.temple.edu/lammps-ro/trunk@12067 f3b2605a-c512-4ea7-a41b-209d697bcdaa
parent c4c6bae7
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
Showing
with 7 additions and 7 deletions
bench/GPU/README
+ 7
− 7
View file @ 63aad352
...@@ -20,10 +20,10 @@ summary description. ...@@ -20,10 +20,10 @@ summary description.
------------------------------------------------------------------------ ------------------------------------------------------------------------
If the script has "cpu" in its name, it is meant to be run in CPU-only If the script has "cpu" in its name, it is meant to be run in CPU-only
mode. For example: mode (without using the GPU or USER-CUDA styles). For example:
mpirun -np 1 ../lmp_linux_double -c off -v x 8 -v y 8 -v z 8 -v t 100 < in.lj.cpu mpirun -np 1 ../lmp_linux_double -v x 8 -v y 8 -v z 8 -v t 100 < in.lj.cpu
mpirun -np 12 ../lmp_linux_double -c off -v x 16 -v y 16 -v z 16 -v t 100 < in.lj.cpu mpirun -np 12 ../lmp_linux_double -v x 16 -v y 16 -v z 16 -v t 100 < in.lj.cpu
The "xyz" settings determine the problem size. The "t" setting The "xyz" settings determine the problem size. The "t" setting
determines the number of timesteps. determines the number of timesteps.
...@@ -33,9 +33,9 @@ determines the number of timesteps. ...@@ -33,9 +33,9 @@ determines the number of timesteps.
If the script has "gpu" in its name, it is meant to be run using If the script has "gpu" in its name, it is meant to be run using
the GPU package. For example: the GPU package. For example:
mpirun -np 12 ../lmp_linux_single -sf gpu -c off -v g 1 -v x 32 -v y 32 -v z 64 -v t 100 < in.lj.gpu mpirun -np 12 ../lmp_linux_single -sf gpu -v g 1 -v x 32 -v y 32 -v z 64 -v t 100 < in.lj.gpu
mpirun -np 8 ../lmp_linux_mixed -sf gpu -c off -v g 2 -v x 32 -v y 32 -v z 64 -v t 100 < in.lj.gpu mpirun -np 8 ../lmp_linux_mixed -sf gpu -v g 2 -v x 32 -v y 32 -v z 64 -v t 100 < in.lj.gpu
The "xyz" settings determine the problem size. The "t" setting The "xyz" settings determine the problem size. The "t" setting
determines the number of timesteps. The "np" setting determines how determines the number of timesteps. The "np" setting determines how
...@@ -49,9 +49,9 @@ than GPUs (both per compute node) with the GPU package. ...@@ -49,9 +49,9 @@ than GPUs (both per compute node) with the GPU package.
If the script has "cuda" in its name, it is meant to be run using If the script has "cuda" in its name, it is meant to be run using
the USER-CUDA package. For example: the USER-CUDA package. For example:
mpirun -np 1 ../lmp_linux_single -sf cuda -v g 1 -v x 16 -v y 16 -v z 16 -v t 100 < in.lj.cuda mpirun -np 1 ../lmp_linux_single -c on -sf cuda -v g 1 -v x 16 -v y 16 -v z 16 -v t 100 < in.lj.cuda
mpirun -np 2 ../lmp_linux_double -sf cuda -v g 2 -v x 32 -v y 64 -v z 64 -v t 100 < in.eam.cuda mpirun -np 2 ../lmp_linux_double -c on -sf cuda -v g 2 -v x 32 -v y 64 -v z 64 -v t 100 < in.eam.cuda
The "xyz" settings determine the problem size. The "t" setting The "xyz" settings determine the problem size. The "t" setting
determines the number of timesteps. The "np" setting determines how determines the number of timesteps. The "np" setting determines how
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment