Intel DML v1.0.0

Functionality

• Added Benchmark Framework with limited support. Refer to the Benchmark Framework Guide in the documentation for details regarding what is supported and how it can be used.
• Added no-operation (no-op) support to High-Level API that can be used in Batch operation as Fence.
• Added support of umonitor/umwait to Low-Level Job API (refer to dml_wait_mode_t enum).
• Added DML_MIN_BATCH_SIZE macro to expose the minimum required batch size.
• Added more status codes reporting for Low-Level Job API to allow reporting of all Intel DSA statuses.
   

Usability and Documentation

• Removed limitation that libaccel-config.so.1 must be placed in /usr/lib64/ to execute an application that uses Intel(R) DML. Now user can specify its location using LD_LIBRARY_PATH environment variable.
• Introduced the -DDML_BUILD_{TESTS, EXAMPLES} option (by default, is ON). -DDML_BUILD_TESTS=OFF enables you to build the library without testing from directly downloadable files (.tar, .tgz).
• Improved High-Level API examples by setting the execution path based on a command-line argument instead of hardcoding to use the Software Path.
• Restructured documentation and introduced general improvements and updates.

Deprecated Functionality

• Removed dml_get_limits(...) service function.
• Removed EFFICIENT_WAIT build option. Now user should set DML_WAIT_MODE_UMWAIT (refer to dml_wait_mode_t enum) when using Low-Level Job API in order to enable umonitor/umwait.

Breaking Changes

• Changed API for Low-Level API dml_execute_job(...) and dml_wait_job(...) to include dml_wait_mode_t wait_mode parameter.

Bug Fixes

• Fixed GCC* 11 build failures caused by missing headers.
• Fixed incorrect queue submission mechanism that might have led to segmentation fault with previous DML releases.

Known issues/limitations

• Intel DML could be built from downloadable files directly (.tar, .tgz) only without tests and benchmark frameworks using the -DDML_BUILD_TESTS=OFF build option. They require submodules that are not included in the archives on GitHub* during release creation.
• Known test failures for Hardware Path are listed below.
  • dml_cache_flush.ta_do_not_invalidate
  • dmlhl_cache_flush/{2, 3}.dont_invalidate
  • transfer_size/cache_flush.success/{1, 3, 5, 7, 9, 11, 13}
  • alignment/cache_flush.success/{1, 3, 5, 7}
  • create_delta.page_fault_{read_first, read_second, write}