-
Notifications
You must be signed in to change notification settings - Fork 112
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[ur] Cleanup inconsistent file properties
* Remove the executable bit from source files * Run `dos2unix` on all source files
- Loading branch information
Showing
4 changed files
with
60 additions
and
60 deletions.
There are no files selected for viewing
116 changes: 58 additions & 58 deletions
116
scripts/core/EXP-USM-IMPORT-RELEASE.rst
100755 → 100644
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,58 +1,58 @@ | ||
|
||
<% | ||
OneApi=tags['$OneApi'] | ||
x=tags['$x'] | ||
X=x.upper() | ||
%> | ||
.. _experimental-usm-import-release: | ||
|
||
================== | ||
USM Import/Release | ||
================== | ||
|
||
.. warning:: | ||
|
||
Experimental features: | ||
|
||
* May be replaced, updated, or removed at any time. | ||
* Do not require maintaining API/ABI stability of their own additions over | ||
time. | ||
* Do not require conformance testing of their own additions. | ||
|
||
|
||
Data transfer between Host and Device is most efficient when source and | ||
destination are both allocated in USM memory. | ||
In situations where host data will participate in host/device transfers | ||
and the host data allocation is under user control, USM functions | ||
such as malloc_host could be used to allocate USM memory instead of | ||
system memory. | ||
However, this is not always possible if the source code where the allocation | ||
is made is not available, or source code changes are prohibited for portability | ||
reasons. | ||
In these situations a mechanism to temporarily promote system memory to USM | ||
for the duration of the host/device data transfers is useful for maximizing | ||
data transfer rate. | ||
|
||
|
||
Import Host Memory into USM | ||
=========================== | ||
|
||
Import a range of host memory into USM. | ||
|
||
.. parsed-literal:: | ||
// Import into USM | ||
${x}USMImportExp(hContext, hostPtr, size); | ||
Release Host Memory Previously Imported into USM | ||
================================================ | ||
|
||
Release from USM a range of memory that had been previously imported | ||
into USM. | ||
|
||
|
||
.. parsed-literal:: | ||
// Release from USM | ||
${x}USMReleaseExp(hContext, hostPtr); | ||
|
||
<% | ||
OneApi=tags['$OneApi'] | ||
x=tags['$x'] | ||
X=x.upper() | ||
%> | ||
.. _experimental-usm-import-release: | ||
|
||
================== | ||
USM Import/Release | ||
================== | ||
|
||
.. warning:: | ||
|
||
Experimental features: | ||
|
||
* May be replaced, updated, or removed at any time. | ||
* Do not require maintaining API/ABI stability of their own additions over | ||
time. | ||
* Do not require conformance testing of their own additions. | ||
|
||
|
||
Data transfer between Host and Device is most efficient when source and | ||
destination are both allocated in USM memory. | ||
In situations where host data will participate in host/device transfers | ||
and the host data allocation is under user control, USM functions | ||
such as malloc_host could be used to allocate USM memory instead of | ||
system memory. | ||
However, this is not always possible if the source code where the allocation | ||
is made is not available, or source code changes are prohibited for portability | ||
reasons. | ||
In these situations a mechanism to temporarily promote system memory to USM | ||
for the duration of the host/device data transfers is useful for maximizing | ||
data transfer rate. | ||
|
||
|
||
Import Host Memory into USM | ||
=========================== | ||
|
||
Import a range of host memory into USM. | ||
|
||
.. parsed-literal:: | ||
// Import into USM | ||
${x}USMImportExp(hContext, hostPtr, size); | ||
Release Host Memory Previously Imported into USM | ||
================================================ | ||
|
||
Release from USM a range of memory that had been previously imported | ||
into USM. | ||
|
||
|
||
.. parsed-literal:: | ||
// Release from USM | ||
${x}USMReleaseExp(hContext, hostPtr); | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
|
||
|
||
<% | ||
OneApi=tags['$OneApi'] | ||
x=tags['$x'] | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
|
||
|
||
<% | ||
OneApi=tags['$OneApi'] | ||
x=tags['$x'] | ||
|
Empty file.