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
This commit was created on GitHub.com and signed with GitHub’s verified signature.
The key has expired.
Usability and Documentation
Changed libaccel-config.so to a build time dependency on Linux instead of loading it for Hardware Path execution at runtime, it is now required to add -laccel-config when building the application with QPL
Fixed duplications in status codes documentation page in Developer Reference
Deprecated Functionality
Dropped support of qpl_op_set_membership, qpl_op_find_unique and qpl_op_rle_burst analytic operations
Dropped support of zero compression: qpl_op_z_compress{16, 32} and qpl_op_z_decompress{16, 32}
Bug Fixes
Changed accelerator dispatching to use lazy initialization with locks to ensure thread safety. Previous behavior might result in crashes on user's side when they fork a child process to submit job to the accelerator
Fixed non-optimal Huffman Only compression when executing on Software Path
Fixed incorrect mapping of accelerator status codes to library status codes which previously resulted in returning undocumented error to the user
Known issues/limitations
Intel QPL cannot be built from direct downloadable files (.tar, .tgz) since it has submodules which are not included to the archives by GitHub during release creation
Internal error code QPL_STS_INTERNAL_ERROR has been moved from error code 222 to error code 6. This could affect users having a hardcoded check for error 222
On Linux libaccel-config.so must be placed in /usr/lib64/ to build and run Intel QPL, even if only the Software Path execution is used