You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I get an unexpected internal library error when executing a dml::mem_copy with a too large byte size (compared to the max_transfer_size specified in the accel-config configuration file).
How to reproduce
(see below for system information)
Unpack the attached archive and cd into the contained directory
Run sudo bash ./setup.sh, to setup the environment.
Compile: cmake . cmake --build .
And run sudo ./program > result
For information on compile options, issued operations, execution path, etc., please refer to the attached source code.
Error description
After a few successful submissions (where the submission size is less than the configured max_transfer_size, configured in config.conf), the code produces internal library errors (dml::status_code::error) for all submissions where the submitted byte size is greater than max_transfer_size.
Make the library more robust against this type of error, and make debugging easier. It is not intuitive to re-check the size of submissions when the API returns an internal error, especially when there is a more appropriate error like dml::status_code::bad_size.
I get an unexpected internal library error when executing a dml::mem_copy with a too large byte size (compared to the max_transfer_size specified in the
accel-config
configuration file).How to reproduce
(see below for system information)
cd
into the contained directorysudo bash ./setup.sh
, to setup the environment.cmake .
cmake --build .
sudo ./program > result
For information on compile options, issued operations, execution path, etc., please refer to the attached source code.
Error description
After a few successful submissions (where the submission size is less than the configured max_transfer_size, configured in config.conf), the code produces internal library errors (dml::status_code::error) for all submissions where the submitted byte size is greater than max_transfer_size.
With reference to https://intel.github.io/DML/documentation/api_docs/high_level_api.html#operation-status-values I would expect to get an error like dml::status_code::bad_size (Invalid byte size was specified).
Use Case
Make the library more robust against this type of error, and make debugging easier. It is not intuitive to re-check the size of submissions when the API returns an internal error, especially when there is a more appropriate error like dml::status_code::bad_size.
System Information
OS Info
OS name
kernel version
6.6.13-amd64
accel-config version
4.1.3.git71676025
CPU model
DML version
Latest (1.2.0), Date: 2024-12-09
Commit Hash: f59ed47
DSA_reproduce_error.zip
The text was updated successfully, but these errors were encountered: