Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
lammps
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
multiscale
lammps
Commits
3b1b9a2c
Commit
3b1b9a2c
authored
7 years ago
by
Axel Kohlmeyer
Browse files
Options
Downloads
Patches
Plain Diff
replace non-ASCII quotation marks with ASCII equivalent
parent
1bd9e175
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/src/accelerate_kokkos.txt
+7
-7
7 additions, 7 deletions
doc/src/accelerate_kokkos.txt
with
7 additions
and
7 deletions
doc/src/accelerate_kokkos.txt
+
7
−
7
View file @
3b1b9a2c
...
@@ -326,9 +326,9 @@ include both "Cuda" and "OpenMP", as is the case for /src/MAKE/OPTIONS/Makefile.
...
@@ -326,9 +326,9 @@ include both "Cuda" and "OpenMP", as is the case for /src/MAKE/OPTIONS/Makefile.
KOKKOS_DEVICES=Cuda,OpenMP :pre
KOKKOS_DEVICES=Cuda,OpenMP :pre
The suffix
/kk
is equivalent to
/kk/device
, and for Kokkos CUDA,
The suffix
"
/kk
"
is equivalent to
"
/kk/device
"
, and for Kokkos CUDA,
using the
-sf kk
in the command line gives the default CUDA version everywhere.
using the
"
-sf kk
"
in the command line gives the default CUDA version everywhere.
However, if the
/kk/host
suffix is added to a specific style in the input
However, if the
"
/kk/host
"
suffix is added to a specific style in the input
script, the Kokkos OpenMP (CPU) version of that specific style will be used instead.
script, the Kokkos OpenMP (CPU) version of that specific style will be used instead.
Set the number of OpenMP threads as "t Nt" and the number of GPUs as "g Ng"
Set the number of OpenMP threads as "t Nt" and the number of GPUs as "g Ng"
...
@@ -338,16 +338,16 @@ For example, the command to run with 1 GPU and 8 OpenMP threads is then:
...
@@ -338,16 +338,16 @@ For example, the command to run with 1 GPU and 8 OpenMP threads is then:
mpiexec -np 1 lmp_kokkos_cuda_openmpi -in in.lj -k on g 1 t 8 -sf kk :pre
mpiexec -np 1 lmp_kokkos_cuda_openmpi -in in.lj -k on g 1 t 8 -sf kk :pre
Conversely, if the
-sf kk/host
is used in the command line and then the
Conversely, if the
"
-sf kk/host
"
is used in the command line and then the
/kk
or
/kk/device
suffix is added to a specific style in your input script,
"
/kk
"
or
"
/kk/device
"
suffix is added to a specific style in your input script,
then only that specific style will run on the GPU while everything else will
then only that specific style will run on the GPU while everything else will
run on the CPU in OpenMP mode. Note that the execution of the CPU and GPU
run on the CPU in OpenMP mode. Note that the execution of the CPU and GPU
styles will NOT overlap, except for a special case:
styles will NOT overlap, except for a special case:
A kspace style and/or molecular topology (bonds, angles, etc.) running on
A kspace style and/or molecular topology (bonds, angles, etc.) running on
the host CPU can overlap with a pair style running on the GPU. First compile
the host CPU can overlap with a pair style running on the GPU. First compile
with
--default-stream per-thread
added to CCFLAGS in the Kokkos CUDA Makefile.
with
"
--default-stream per-thread
"
added to CCFLAGS in the Kokkos CUDA Makefile.
Then explicitly use the
/kk/host
suffix for kspace and bonds, angles, etc.
Then explicitly use the
"
/kk/host
"
suffix for kspace and bonds, angles, etc.
in the input file and the "kk" suffix (equal to "kk/device") on the command line.
in the input file and the "kk" suffix (equal to "kk/device") on the command line.
Also make sure the environment variable CUDA_LAUNCH_BLOCKING is not set to "1"
Also make sure the environment variable CUDA_LAUNCH_BLOCKING is not set to "1"
so CPU/GPU overlap can occur.
so CPU/GPU overlap can occur.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment