-
Notifications
You must be signed in to change notification settings - Fork 548
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs: Add xnack to unified memory page #3732
base: docs/develop
Are you sure you want to change the base?
Conversation
7cc8f4b
to
bb25693
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some small suggestions
docs/how-to/hip_runtime_api/memory_management/unified_memory.rst
Outdated
Show resolved
Hide resolved
docs/how-to/hip_runtime_api/memory_management/unified_memory.rst
Outdated
Show resolved
Hide resolved
docs/how-to/hip_runtime_api/memory_management/unified_memory.rst
Outdated
Show resolved
Hide resolved
docs/how-to/hip_runtime_api/memory_management/unified_memory.rst
Outdated
Show resolved
Hide resolved
docs/how-to/hip_runtime_api/memory_management/unified_memory.rst
Outdated
Show resolved
Hide resolved
docs/how-to/hip_runtime_api/memory_management/unified_memory.rst
Outdated
Show resolved
Hide resolved
docs/how-to/hip_runtime_api/memory_management/unified_memory.rst
Outdated
Show resolved
Hide resolved
docs/how-to/hip_runtime_api/memory_management/unified_memory.rst
Outdated
Show resolved
Hide resolved
docs/how-to/hip_runtime_api/memory_management/unified_memory.rst
Outdated
Show resolved
Hide resolved
docs/how-to/hip_runtime_api/memory_management/unified_memory.rst
Outdated
Show resolved
Hide resolved
0498b4d
to
5931eb6
Compare
docs/how-to/hip_runtime_api/memory_management/unified_memory.rst
Outdated
Show resolved
Hide resolved
docs/how-to/hip_runtime_api/memory_management/unified_memory.rst
Outdated
Show resolved
Hide resolved
docs/how-to/hip_runtime_api/memory_management/unified_memory.rst
Outdated
Show resolved
Hide resolved
docs/how-to/hip_runtime_api/memory_management/unified_memory.rst
Outdated
Show resolved
Hide resolved
5931eb6
to
ed1171a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few comments, but overall it looks good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fir line 13:
space and dedicated physical memory backing it up, for example normal RAM for CPUs and
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For line 49:
the host or another device, on which the memory is located. The page is then
XNACK | ||
----- | ||
|
||
On specific GPU architectures (which is referenced in the previous table), there is an |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On specific GPU architectures (which is referenced in the previous table), there is an | |
On specific GPU architectures (referenced in the previous table), there is an |
Depending on the system, page migration may be disabled by default in which case managed | ||
memory will act like pinned host memory and suffer degraded performance. | ||
|
||
**XNACK** describes the GPU's ability to retry memory accesses that failed due to a page fault |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Although it is footnoted in the previous table, I would add here that you need to enable XNACK ability by setting XNACK=1 environment variable.
Name: amdgcn-amd-amdhsa--gfx90a:sramecc+:xnack- | ||
|
||
Here, ``xnack-`` means that XNACK is available but is disabled by default. | ||
Turning on XNACK by setting the environment variable ``HSA_XNACK=1`` gives |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here it says that XNACK is enabled with HSA_XNACK=1, but up above it is simply XNACK=1. Which is correct?
Add sub-section about XNACK (along with a small example) to the
unified_memory.rst
page.