GitPlanet

Cheap and reliable Node.js hosting starts at $3/month, and $1/month static HTML hosting

Created with love in Canada, visit hostnodejs.com today

Feel like to post an Ad? Learn Details
All Projects → intel → Qat_engine

intel / Qat_engine

Licence: other

Programming Languages

c
50402 projects - #5 most used programming language

Intel® QuickAssist Technology(QAT) OpenSSL* Engine

Table of Contents

Licensing

The Licensing of the files within this project is split as follows:

Intel® QuickAssist Technology(QAT) OpenSSL* Engine - BSD License. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/). Please see the LICENSE and LICENSE.OPENSSL file contained in the top level folder. Further details can be found in the file headers of the relevant files.

Example Intel® Contiguous Memory Driver contained within the folder qat_contig_mem - GPLv2 License. Please see the file headers within the qat_contig_mem folder, and the full GPLv2 license contained in the file LICENSE.GPL within the qat_contig_mem folder.

Example Intel® QuickAssist Technology Driver Configuration Files contained within the folder hierarchy qat - Dual BSD/GPLv2 License. Please see the file headers of the configuration files, and the full GPLv2 license contained in the file LICENSE.GPL within the qat folder.

Features

  • Synchronous and Asynchronous Operation
  • Asymmetric PKE Offload
    • RSA Support for Key Sizes 1024/2048/4096.
    • DH Support for Key Sizes 768/1024/1536/2048/3072/4096.
    • DSA Support for Key Sizes 160/1024, 224/2048, 256/2048, 256/3072.
    • ECDH Support for the following curves:
      • NIST Prime Curves: P-192/P-224/P-256/P-384/P-521.
      • NIST Binary Curves: B-163/B-233/B-283/B-409/B-571.
      • NIST Koblitz Curves: K-163/K-233/K-283/K-409/K-571.
      • Montgomery EC Curves: X25519/X448 (ECX).
    • ECDSA Support for the following curves:
      • NIST Prime Curves: P-192/P-224/P-256/P-384/P-521.
      • NIST Binary Curves: B-163/B-233/B-283/B-409/B-571.
      • NIST Koblitz Curves: K-163/K-233/K-283/K-409/K-571.
  • Symmetric Chained Cipher Offload with pipelining capability:
    • AES128-CBC-HMAC-SHA1/AES256-CBC-HMAC-SHA1.
    • AES128-CBC-HMAC-SHA256/AES256-CBC-HMAC-SHA256.
  • Pseudo Random Function (PRF) offload.
  • HMAC Key Derivation Function (HKDF) Offload.
  • Support for the Intel® QuickAssist Technology Driver Heartbeat feature.
  • Multi-buffer Software optimization. (Software Optimization using Intel® Crypto Multi-buffer Library)
    • RSA Support for Key size 2048
    • ECDH Support for Montgomery EC Curve: X25519
  • AES128-GCM, AES192-GCM and AES256-GCM. (Software Optimization using Intel® Multi-Buffer Crypto for IPsec Library)

Note: RSA Padding schemes are handled by OpenSSL rather than offloaded, so the engine supports the same padding schemes as OpenSSL does natively.

Hardware Requirements

This Intel® QAT OpenSSL* Engine supports crypto offload to the following acceleration devices:

Software Requirements

Successful operation of this release requires a software tool chain that supports OpenSSL* 1.1.1 or OpenSSL* 1.1.0. This release was validated on the following:

  • Operating system: CentOS* 7.4 64-bit version & FreeBSD* 11.3 64-bit version
  • Kernel: GNU*/Linux* 3.10.0-693
  • Intel® Communications Chipset C62X Series Software for Linux*, version 4.11
  • Intel® Communications Chipset C62X Series Software for FreeBSD*, version 3.8
  • OpenSSL* 1.1.1

It is recommended that the Intel® QAT OpenSSL* Engine is built against GNU* C Library version 2.23 or later to take advantage of AVX-512 optimizations if supported by your processor (Linux Specific).

Additional Information

Additional Information on integrating the Intel&reg QAT OpenSSL* Engine with NGINX* including an asynchronous fork of NGINX* can be found at the following Github* repository:

Limitations

  • When using TLS 1.3 only asymmetric PKE and HKDF offload is supported. The symmetric ciphers currently offloaded are not compatible with the TLS 1.3 symmetric ciphers which are ChaCha-Poly based.
  • When forking within an application it is not valid for a cryptographic operation to be started in the parent process, and completed in the child process.
  • Only one level of forking is permitted, if a child process forks again then the Intel® QAT OpenSSL* Engine will not be available in that forked process.
  • The function ASYNC_WAIT_CTX_get_changed_fds contained in OpenSSL* 1.1.0 might return incorrect values in the case of failures during the submission of operations to the hardware accelerator. This could result in errors at the application level. The fix has been delivered in OpenSSL* 1.1.0e and OpenSSL* 1.1.1. All previous versions of the library are affected. For more information, please refer to the following pull request on Github: Fix waitctx fds removing the fd from the list #2581
  • Event driven mode of polling operation is not supported in the FreeBSD Operating system or in the qatlib RPM.
  • qat_contig_mem memory driver is not supported when running under FreeBSD Operating system or in the qatlib RPM. The default is to use the USDM memory driver supplied as part of the Intel® QAT Driver.
  • Support for cipher AES-128-CBC-HMAC-SHA1 and its related ciphers was broken in release OpenSSL* 1.1.1d. This was later fixed in OpenSSL* 1.1.1e release.
  • Support for Multi-buffer offload is extended to RSA 2k only. Other key sizes will use the standard OpenSSL implementation when this feature is enabled.
  • X25519/X448 support is available only from version 4.9 of the Intel® QAT driver for Linux. Use --disable-qat_ecx in the Intel® QAT OpenSSL* Engine configure when building against earlier versions of the Linux driver.
  • Support for qaeMemFreeNonZeroNUMA() USDM API is available only from version 4.10 of the Intel® QAT driver for Linux. Use --with-cc-opt="-DQAT_DISABLE_NONZERO_MEMFREE" in the Intel® QAT OpenSSL* Engine configuration when building against earlier versions of the Linux driver.

Installation Instructions

Build Intel® QuickAssist Technology Driver

Please follow the instructions contained in:

For Intel® Xeon® with Intel® C62X Series Chipset: For Intel® Atom™ Processor: For Intel® Communications Chipset 8925 to 8955 Series: Intel® QuickAssist Technology Software for Linux* - Getting Started Guide - HW version 1.7 (336212)

Other technical collaterals of the Intel® QuickAssist Technology driver can be found in the below 01.org page.

Intel® QuickAssist Technology

Build OpenSSL*

This step is not needed if building the Intel® QAT OpenSSL* Engine against system prebuilt OpenSSL* 1.1.1 and thereby installs engine library in the system OpenSSL engines directory.

Clone OpenSSL* from Github* at the following location:

git clone https://github.com/openssl/openssl.git

It is recommended to checkout and build against the OpenSSL* 1.1.1 git tag specified in the release notes. Versions of OpenSSL* before OpenSSL* 1.1.0 are not supported.

Due to the nature of the Intel® QAT OpenSSL* Engine being a dynamic engine it can only be used with shared library builds of OpenSSL*.

Note: The OpenSSL* 1.1.0 and 1.1.1 baselines build as a shared library by default now so there is no longer any need to specify the shared option when running ./config.

Note: It is not recommended to install the accelerated version of OpenSSL* as your default system library. If you do, you may find that acceleration is used unexpectedly by other applications on the system resulting in undesired/unsupported behaviour. The --prefix can be used with the ./config command to specify the location that make install will copy files to. Please see the OpenSSL* INSTALL file for full details on usage of the --prefix option.

From OpenSSL* version 1.1.0c onwards, automatic RPATH has been removed. The reason for this is that before OpenSSL* version 1.1.0, binaries were installed in a non-standard location by default, and runpath directories were therefore added in those binaries, to make sure the executables would be able to find the shared libraries they were linked with. However, with OpenSSL* version 1.1.0 and on, binaries are installed in standard directories by default, and the addition of runpath directories is not done automatically. If you wish to install OpenSSL* in a non-standard location (recommended), the runpath directories can be specified via the OpenSSL* Configure command, which recognises the arguments -rpath and -R to support user-added rpaths. For convenience, a Makefile variable LIBRPATH has also been added which is defined as the full path to a subdirectory of the installation directory. The subdirectory is named lib by default. If you do not wish to use LIBRPATH, the rpath can be specified directly. The syntax for specifying a rpath is as follows:

./config [options] -Wl,-rpath,\${LIBRPATH}

The -rpath can be replaced with -R for brevity. If you do not wish to use the built-in variable LIBRPATH, the syntax for specifying a rpath of /usr/local/ssl/lib for example would be:

./config [options] -Wl,-rpath,/usr/local/ssl/lib

Alternatively, you can specify the rpath by adding it to the environment variable LD_LIBRARY_PATH via the command:

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:`RPATH`

where RPATH is the full path(s) to the shared libraries. This is not the preferred method though.

The following example is assuming:

  • The OpenSSL* source was cloned from Github* to its own location at the root of the drive: /.
  • You want OpenSSL* to be installed to /usr/local/ssl.

An example build would be:

cd /openssl
./config --prefix=/usr/local/ssl -Wl,-rpath,\${LIBRPATH}
make depend (if recommended by the OpenSSL\* build system)
make
make install

As the Intel® QAT OpenSSL* Engine will be built as a dynamic engine it is important to tell OpenSSL* where to find the dynamic engines at runtime. This is achieved by exporting the following environment variable (assuming the example paths above):

export OPENSSL_ENGINES=/usr/local/ssl/lib/engines-1.1

Note: This variable will need to be present in the environment whenever the engine is used.

Further information on building OpenSSL* can be found in the INSTALL file distributed with the OpenSSL* source code or on the official OpenSSL* Wiki in the Compilation and Installation section: https://wiki.openssl.org/index.php/Compilation_and_Installation

Clone the Intel® QuickAssist Technology OpenSSL* Engine

Clone the Github* repository containing the Intel® QAT OpenSSL* Engine:

git clone https://github.com/intel/QAT_Engine.git

The repository can be cloned to either a subdirectory within the OpenSSL* repository, for instance if the OpenSSL* source is located at /openssl then the engine could be cloned at /openssl/engines, or to its own unique location on the file system, for instance within /. In either case the engine will not be built as part of the OpenSSL* build and will require building manually.

Build and install a contiguous memory driver

The Intel® QAT API requires many of the data structures (those that will be passed to the hardware) to be allocated in contiguous pinned memory in order to support DMA operations. You must either supply your own contiguous memory driver and make changes to the engine to make use of it or use one of the following drivers:

(Optional) Load the User Space DMA-able Memory (USDM) Component

The Intel® QAT Driver HW Version 1.7 comes with its own contiguous pinned memory driver that is compatible with the Intel® QAT OpenSSL* Engine. The USDM component is of a higher quality than the qat_contig_mem driver provided within the Intel® QAT OpenSSL* Engine, and is the preferred option. The USDM component is used by the Intel® QAT Driver HW Version 1.7 itself, and also has the following additional features:

  • Support for virtualization
  • Support for configurable slab sizes
  • Support for configurable secure freeing of memory (overwrite with zeros)
  • Support for configurable slab caching
  • Support for newer kernels

The USDM component is located within the Intel® QAT Driver HW Version 1.7 source code in the following subdirectory: quickassist/utilities/libusdm_drv. As the USDM component is also used by the 1.7 driver itself it will have already been built when the driver was built. It may also already be loaded as well, and you can check by running lsmod and looking for usdm_drv in the list. If not present it can be loaded as follows:

insmod ./usdm_drv.ko

(Optional) Build and load the example contiguous memory driver - qat_contig_mem

This step is not needed if using the default USDM driver above. The Intel® QAT OpenSSL* Engine comes with an example kernel space contiguous memory driver that can be used to try out operation of the engine. It is considered to be an example only and is not written to be a production quality driver. The use of the qat_contig_mem driver can be enabled using the configure option --enable-qat_contig_mem that tells the build that the Intel® QAT OpenSSL* Engine should be compiled to use the qat_contig_mem component instead of the USDM memory driver above.

The following example is assuming:

  • The Intel® QAT OpenSSL* Engine was cloned to its own location at the root of the drive: /.

To build/install the qat_contig_mem driver follow these steps:

cd /QAT_Engine/qat_contig_mem
make
make load
make test

The expected output from make test should be something similar to the following:

seg mapped to 0x7f9eedd6e000, virtualAddress in seg 0xffff880ac9c0c000,
length 64
Hello world!
# PASS Verify for QAT Contig Mem Test

Build the Intel® QuickAssist Technology OpenSSL* Engine

The following example is assuming:

  • The Intel® QAT OpenSSL* Engine was cloned to its own location at the root of the drive: /.
  • The Intel® QAT Driver HW Version 1.7 was unpacked within /QAT and using the USDM component.
  • An Intel® Communications Chipset C62X Series device is fitted.
  • OpenSSL* 1.1.1 built from source is being used and installed to /usr/local/ssl.

To build and install the Intel® QAT OpenSSL* Engine:

cd /QAT_Engine
./autogen.sh
./configure \
--with-qat_dir=/QAT \
--with-openssl_install_dir=/usr/local/ssl
make
make install

In the above example this will create the file qatengine.so and copy it to /usr/local/ssl/lib/engines-1.1. ./autogen.sh will regenerate autoconf tools files. The prerequisite to run autogen.sh is to have autotools (autoconf, automake, libtool and pkg-config) installed in the system.

Note: When building it is possible to specify command line options that can be used to turn engine functionality on and off. Please see the Intel® QAT OpenSSL* Engine Build Options section below for a full description of the options that can be specified.

An example to build and install the Intel® QAT OpenSSL* Engine against a prebuilt OpenSSL* 1.1.1 from the system is as follows. It assumes that:

  • The Intel® QAT OpenSSL* Engine was cloned to its own location at the root of the drive: /.
  • The Intel® QAT Driver HW Version 1.7 was unpacked within /QAT and using the USDM component.
  • Prebuilt OpenSSL* (both library and devel RPM packages) are installed in the system and the OpenSSL* version is in the 1.1.1 series.

To build and install the Intel® QAT OpenSSL* Engine:

cd /QAT_Engine
./autogen.sh
./configure  --with-qat_dir=/QAT
make
make install

In the above example this will create the file qatengine.so and copy it to the engines dir of the system which can be checked using pkg-config --variable=enginesdir libcrypto.

If OpenSSL* version in the system can not be updated to 1.1.1 series, then the engine needs to be built from source using the option --with-openssl_install_dir. An additional option --with-openssl_dir pointing to the top directory of the OpenSSL* source needs to be provided for building against OpenSSL* 1.1.0 as the engine err files need to be regenerated for 1.1.0.

Copy the Intel® QuickAssist Technology Driver config files

The Intel® QAT OpenSSL* Engine comes with some example conf files to use with the Intel® QAT Driver. The Intel® QAT OpenSSL* Engine will not function with the default Intel® QAT Driver conf file because the default conf does not contain a [SHIM] section which the Intel® QAT OpenSSL* Engine requires by default. The default section name in the QAT OpenSSL* Engine can be modified if required by either using the engine ctrl command SET_CONFIGURATION_SECTION_NAME or by setting the environment variable "QAT_SECTION_NAME". The conf files are located at:

/path/to/qat_engine/qat/config

The files are grouped by acceleration device(dh895xcc or c6xx or c3xxx), please choose the files appropriate to your acceleration device only.

The files are also split into multi_process_optimized and multi_thread_optimized.

If your application runs one (or very few) processes, but has multiple threads in each process, each accessing the acceleration device, then you should pick the multi_thread_optimized config files. An example of this is a webserver that creates a new thread for each incoming connection.

If your application scales by creating new processes, then you should pick the multi_process_optimized config files. An example of this is an event driven application that runs as a single thread in an event loop. In this type of application it is usual for the application to create at least one new process for each cpu core you want to utilize.

There are also similar config files for if you are using the event driven polling feature of the Intel® QAT Driver contained in multi_thread_event-driven_optimized and multi_process_event-driven_optimized respectively. Event driven config files are only supported in Linux. Once you have decided which config file you should use, or created your own you should follow the procedure below to install it:

  1. Stop the acceleration driver as described in the Section 3.4 Starting/Stopping the Acceleration software from the Getting Started Guide - HW version 1.7 (336212)

  2. Copy the appropriate .conf file to /etc

  3. Start the acceleration driver as described in the Section 3.4 Starting/Stopping the Acceleration software from the Getting Started Guide - HW version 1.7 (336212)

Test the Intel® QuickAssist Technology OpenSSL* Engine

Run this command to check if the Intel® QAT OpenSSL* Engine is loaded correctly:

cd /path/to/openssl_install/bin
./openssl engine -t -c -vvvv qatengine
(qatengine) Reference implementation of QAT crypto engine
 [RSA, DSA, DH, AES-128-CBC-HMAC-SHA1, AES-256-CBC-HMAC-SHA1,
 AES-128-CBC-HMAC-SHA256, AES-256-CBC-HMAC-SHA256,
 TLS1-PRF, HKDF, X25519, X448]
     [ available ]
     ENABLE_EXTERNAL_POLLING: Enables the external polling interface to the engine.
          (input flags): NO_INPUT
     POLL: Polls the engine for any completed requests
          (input flags): NO_INPUT
     SET_INSTANCE_FOR_THREAD: Set instance to be used by this thread
          (input flags): NUMERIC
     GET_NUM_OP_RETRIES: Get number of retries
          (input flags): NO_INPUT
     SET_MAX_RETRY_COUNT: Set maximum retry count
          (input flags): NUMERIC
     SET_INTERNAL_POLL_INTERVAL: Set internal polling interval
          (input flags): NUMERIC
     GET_EXTERNAL_POLLING_FD: Returns non blocking fd for crypto engine
          (input flags): NO_INPUT
     ENABLE_EVENT_DRIVEN_POLLING_MODE: Set event driven polling mode
          (input flags): NO_INPUT
     GET_NUM_CRYPTO_INSTANCES: Get the number of crypto instances
          (input flags): NO_INPUT
     DISABLE_EVENT_DRIVEN_POLLING_MODE: Unset event driven polling mode
          (input flags): NO_INPUT
     SET_EPOLL_TIMEOUT: Set epoll_wait timeout
          (input flags): NUMERIC
     SET_CRYPTO_SMALL_PACKET_OFFLOAD_THRESHOLD: Set QAT small packet threshold
          (input flags): STRING
     ENABLE_INLINE_POLLING: Enables the inline polling mode.
          (input flags): NO_INPUT
     ENABLE_HEURISTIC_POLLING: Enable the heuristic polling mode
          (input flags): NO_INPUT
     GET_NUM_REQUESTS_IN_FLIGHT: Get the number of in-flight requests
          (input flags): NUMERIC
     INIT_ENGINE: Initializes the engine if not already initialized
          (input flags): NO_INPUT
     ENABLE_SW_FALLBACK: Enables the fallback to SW if the acceleration devices go offline
          (input flags): NO_INPUT
     HEARTBEAT_POLL: Check the acceleration devices are still functioning
          (input flags): NO_INPUT
     DISABLE_QAT_OFFLOAD: Perform crypto operations on core
          (input flags): NO_INPUT

Run speed with the Intel® QuickAssist Technology OpenSSL* Engine

cd /path/to/openssl_install/bin

* RSA 2K
  * Asynchronous
  ./openssl speed -engine qatengine -elapsed -async_jobs 72 rsa2048
  * Synchronous
  ./openssl speed -engine qatengine -elapsed rsa2048
  * Software
  ./openssl speed -elapsed rsa2048
* ECDH Compute Key
  * Asynchronous
  ./openssl speed -engine qatengine -elapsed -async_jobs 36 ecdh
  * Synchronous
  ./openssl speed -engine qatengine -elapsed ecdh
  * Software
  ./openssl speed -elapsed ecdh
* Chained Cipher: aes-128-cbc-hmac-sha1
  * Asynchronous
  ./openssl speed -engine qatengine -elapsed -async_jobs 128 -multi 2 -evp aes-128-cbc-hmac-sha1
  * Synchronous
  ./openssl speed -engine qatengine -elapsed -multi 2 -evp aes-128-cbc-hmac-sha1
  * Software
  ./openssl speed -elapsed -multi 2 -evp aes-128-cbc-hmac-sha1

Troubleshooting

The most likely failure point is that the Intel® QAT OpenSSL* Engine is not loading successfully. If this occurs some of the things to check are:

  1. Has the USDM memory driver been loaded successfully? If not the engine will fail to initialise. Check by running lsmod for Linux and kldstat for FreeBSD, usdm_drv should be in the list. If using the alternative qat_contig_mem driver, look for qat_contig_mem.
  2. Has the correct Intel® QAT Driver config file been copied to /etc? Check it has a [SHIM] section and that the Intel® QAT Driver software was restarted so that it picked up the new config file.
  3. Is the Intel® QAT Driver up and running? Check by running adf_ctl, device details along with the state should be state: up. Also check the Intel® QAT Driver software has been started.
  4. Were the paths set correctly so that the qatengine.so engine file was copied to the correct location? Check they really are there.
  5. Has the environment variable OPENSSL_ENGINES been correctly defined and exported to the shell? Also check it is really pointing to the correct location.
  6. If building for OpenSSL 1.1.0 was the configure option --with-openssl_dir specified? (Linux Specific)
  7. If building from OpenSSL prebuilt RPM Package, has the OpenSSL developement packages (openssl-devel for Redhat* based distribution and libssl-devel for Debian* based distribution) been installed ?

If running on a Debian* based OS (Ubuntu* for example) it is possible that the Intel® QAT Driver userspace shared library needed by the Intel® QAT OpenSSL* Engine may not be located even though it has been installed. To resolve this it is recommended to add the /lib64 folder to the LD_LIBRARY_PATH environment variable as follows:

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib64

If building against OpenSSL* 1.1.1 or master branch , it is possible that the OpenSSL* Engine will fail to build with an error message configdata.pm not present in the @INC path. To resolve this, it is recommended to add the OpenSSL source path to the PERL5LIB environment variable as follows:

export PERL5LIB=$PERL5LIB:/path/to/openssl

If seeing failures with USDM memory allocation, either with non-root or root user check memlock limit with ulimit -l and increase the memlock limit to desired value if it is low.

Intel® QuickAssist Technology OpenSSL* Engine Specific Messages

OpenSSL* engines support a mechanism whereby custom messages can be defined for an application to communicate directly with the engine. These messages are typically used in two ways:

  1. Firstly in order to set configuration options. These messages are typically sent before the engine is initialized. Sending these after initialization will typically have no effect.
  2. Secondly in order to control the engine operation. These messages may be sent before initialization or after or both.

The custom message mechanism passes a string to identify the message, and uses a number of parameters to pass information into or out of the engine. It is defined as follows:

ENGINE_ctrl_cmd(<Engine>, <Message String>, <Param 3>,
                <Param 4>, NULL, 0\)

Where:

  • <Engine> is a pointer to the Intel® QAT enabled OpenSSL* Engine.
  • <Message String> is a string representing the message type.
  • <Param 3> is a long that can be used to pass a number, or a pointer can be cast to it.
  • <Param 4> is a void pointer used to pass data structures in.
  • The last two parameters are always NULL and 0 when used with the Intel® QAT OpenSSL* Engine.
Message String: ENABLE_EXTERNAL_POLLING
Param 3:        0
Param 4:        NULL
Description:
    This message is used to enable the external polling mode of operation where
    it becomes the applications responsibility to use the POLL message below to
    check for messages that have been returned from the hardware accelerator.
    It has no parameters or return value.  If required this message must be
    sent after engine creation and before engine initialization.

Message String: POLL
Param 3:        0
Param 4:        pointer to an int
Description:
    This message is used when external polling is enabled to request poll of
    all instances. The status of the request is passed back in the variable
    passed in as Param 4. This message may be sent at any time after engine
    initialization.

Message String: INIT_ENGINE
Param 3:        0
Param 4:        NULL
Description:
    This message is not normally necessary as the engine will get initialized
    either via an ENGINE_init() call or automatically following a fork. This
    message would only be used for performance reasons with an engine compiled
    with --disable-qat_auto_engine_init_on_fork. In that case it may be
    desirable to send this engine message in the child rather than wait for the
    engine to be initialized automatically on the first offloaded crypto
    request.

Message String: SET_INTERNAL_POLL_INTERVAL
Param 3:        unsigned long cast to a long
Param 4:        NULL
Description:
    This message is used to set the interval in nano seconds between polling
    for messages coming back from the hardware accelerator. The value should be
    passed in as Param 3. The default is 10,000, the min value is 1, and
    the max value is 10,000,000. This message can be sent at any time after
    the engine has been created.

Message String: SET_EPOLL_TIMEOUT
Param 3:        unsigned long cast to a int
Param 4:        NULL
Description:
    This message is used to set the timeout in milli seconds used for
    epoll_wait() when event driven polling mode is enabled. The value should be
    passed in as Param 3. The default is 1,000, the min value is 1, and the max
    value is 10,000. This message can be sent at any time after the engine has
    been created. This message is not supported in the FreeBSD operating system
    or in the qatlib RPM.

Message String: ENABLE_EVENT_DRIVEN_POLLING_MODE
Param 3:        0
Param 4:        NULL
Description:
    This message changes the engines mode to use the Intel(R) QAT Drivers
    event driven polling feature. It must be sent if required after engine
    creation but before engine initialization.  It should not be sent after
    engine initialization. This message is not supported in the FreeBSD
    operating system or in the qatlib RPM.

Message String: DISABLE_EVENT_DRIVEN_POLLING_MODE
Param 3:        0
Param 4:        NULL
Description:
    This message changes the engines mode to use the timer based polling
    feature. It must be sent if required after engine creation but before
    engine initialization. It should not be sent after engine initialization.
    This message is not supported in the FreeBSD operating system or in the
    qatlib RPM.

Message String: GET_NUM_CRYPTO_INSTANCES
Param 3:        0
Param 4:        pointer to an int
Description:
    This message is used to retrieve the total number of crypto instances
    available as specified in the Intel(R) QAT Driver config file. The number
    of instances is assigned to the dereferenced int that is passed in as Param
    4. This message is used in conjunction with the GET_POLLING_FD message as in
    event driven polling mode with external polling there is an fd to listen to
    events on for each crypto instance. This message must be sent if required
    after the engine has been initialized.

Message String: GET_EXTERNAL_POLLING_FD
Param 3:        int cast to a long
Param 4:        pointer to an int
Description:
    This message is used to retrieve the file descriptor that can be used for
    event notification when the Intel(R) QAT Driver has had the event driven
    polling feature enabled. The value passed in as Param 3 is the instance to
    retrieve the fd for. The fd is returned by assigning to the dereferenced
    int passed as Param4. When retrieving fd's it is usual to first request how
    many instances there are with the GET_NUM_CRYPTO_INSTANCES message and then
    use a for loop to iterate through the instances starting from 0 and use
    this message to retrieve the fd for each instance. This message must be
    sent if required after the engine has been initialized. This message is
    not supported in the FreeBSD operating system or in the qatlib RPM.

Message String: SET_INSTANCE_FOR_THREAD
Param 3:        long
Param 4:        NULL
Description:
    This message is used to bind the thread to a specific instance number.
    Param 3 contains the instance number to bind to. If required, the message
    must be sent after the engine creation and will automatically trigger the
    engine initialization.

Message String: GET_NUM_OP_RETRIES
Param 3:        0
Param 4:        pointer to an unsigned int
Description:
    This message returns the number of retry operations.  The number is set in
    the variable passed in as Param 4.  This message may be sent at any time
    after engine initialization.

Message String: SET_MAX_RETRY_COUNT
Param 3:        int cast to a long
Param 4:        NULL
Description:
    This message is used for synchronous operations to determine how many times
    the engine should retry a message before flagging a failure. The value
    should be passed in as Param 3. Setting the value to -1 results in infinite
    retries. The default is 5 and the max value is 100,000. This message can be
    sent at any time after the engine is created.

Message String: SET_CRYPTO_SMALL_PACKET_OFFLOAD_THRESHOLD
Param 3:        0
Param 4:        NULL terminated string of cipher algorithm name and threshold
                value. Maximum length is 1024 bytes including NULL terminator.
Description:
    This message is used to set the threshold that determines the size crypto
    packets need to be before they are offloaded to the acceleration device.
    It is not efficient to offload very small packets to the accelerator as to
    do so would take longer to transfer the data to and from the accelerator
    than to encrypt/decrypt using the main CPU. The threshold value can be set
    independently for each EVP_CIPHER operation supported by the engine using
    the following names:
        AES-128-CBC-HMAC-SHA1
        AES-256-CBC-HMAC-SHA1
        AES-128-CBC-HMAC-SHA256
        AES-256-CBC-HMAC-SHA256
    The input format should be a string like this in one line:
        AES-128-CBC-HMAC-SHA1:4096,AES-256-CBC-HMAC-SHA1:8192
    Using a separator ":" between cipher name and threshold value.
    Using a separator "," between different cipher configurations.
    The default threshold value is 2048 bytes, the minimum is 0 bytes and the
    maximum is 16,384.
    The threshold value includes all the bytes that make up the TLS record
    including Record Header (5 bytes), IV (16 bytes), Payload, HMAC (20/32
    bytes), Padding (variable but could be max 255 bytes), and Padding Length
    (1 byte).
    The string should be NULL terminated and not more than 1024 bytes long
    including NULL terminator.
    This message is not supported when the engine is compiled with the flag
    --enable-qat_small_pkt_offload.

Message String: ENABLE_INLINE_POLLING
Param 3:        0
Param 4:        NULL
Description:
    This message is used to enable the inline polling mode of operation where
    a busy loop is used by the Intel(R) QAT OpenSSL* Engine to check for
    messages from the hardware accelerator after requests are sent to it.
    Currently this mode is only available in the synchronous RSA computation.
    It has no parameters or return value. If required this message must be sent
    after engine creation and before engine initialization.

Message String: ENABLE_HEURISTIC_POLLING
Param 3:        0
Param 4:        NULL
Description:
    This message is used to enable the heuristic polling mode of operation where
    the application can use the GET_NUM_REQUESTS_IN_FLIGHT message below to
    retrieve the number of different kinds of in-flight requests and
    intelligently determine the proper moment to perform the polling operation.
    This mode can be regarded as an improvement of the timer-based external
    polling. The external polling mode must be enabled first before enabling
    this mode. If required this message must be sent after engine creation and
    before engine initialization.

Message String: GET_NUM_REQUESTS_IN_FLIGHT
Param 3:        int cast to a long
Param 4:        pointer to an int address
Description:
    This message is used when heuristic polling is enabled to retrieve the
    number of different kinds of in-flight requests.
    The value passed in as param 3 is the indicator for a specific kind of
    request:
        #define GET_NUM_ASYM_REQUESTS_IN_FLIGHT 1
        #define GET_NUM_KDF_REQUESTS_IN_FLIGHT 2
        #define GET_NUM_CIPHER_PIPELINE_REQUESTS_IN_FLIGHT 3
    The first (i.e, value 1) is used to retrieve the number of asymmetric-key
    in-flight requests. The second (i.e, value 2) is used to retrieve the number
    of KDF(PRF and HKDF) in-flight requests.  The last (i.e, value 3) is used to
    retrieve the number of cipher in-flight requests (when the OpenSSL* pipelining
    feature is not used), or the number of in-flight pipelines (when the OpenSSL*
    pipelining feature is used).
    The address of the variable recording the specified info is returned by
    assigning to the dereferenced int address passed as Param 4. This means the
    application can directly use this int address to retrieve the specified info
    afterwards without sending this message again.
    This message may be sent at any time after engine initialization.

Message String: SET_CONFIGURATION_SECTION_NAME
Param 3:        0
Param 4:        NULL terminated string of section name from Intel(R) QAT Driver
                config file. Maximum length is 64 bytes including
                NULL terminator.
Description:
    This message is used to configure the Intel(R) QAT OpenSSL* Engine to use
    the string passed in as parameter 4 to be the name for the Intel(R) QAT
    Driver config section rather than the default `[SHIM]`. It must be sent
    after engine creation but before engine initialization. It should not be
    sent after engine initialization.

Message String: ENABLE_SW_FALLBACK
Param 3:        0
Param 4:        NULL
Description:
    This message is used to enable fallback to software (on-core) of the crypto
    operations normally offloaded to the acceleration devices by the
    Intel&reg; QuickAssist Technology OpenSSL\* Engine.  This command enables
    the software fallback feature - crypto operations will continue to be offloaded
    but, with this feature enabled, in the event the accelerations devices
    subsequently go offline the Intel&reg; QuickAssist Technology OpenSSL\* Engine
    will automatically switch to performing crypto operations on-core.
    If required this message must be sent after engine creation and
    before engine initialization. This message is not supported in the FreeBSD
    operating system or in the qatlib RPM.

Message String: HEARTBEAT_POLL
Param 3:        0
Param 4:        pointer to an int
Description:
    This message is used to check the acceleration devices are still functioning.
    It is normally used in conjunction with the Software Fallback feature
    (see engine command ENABLE_SW_FALLBACK) when using External Polling Mode
    (see engine command ENABLE_EXTERNAL_POLLING). The result of this
    engine specific message (success/failure) is assigned to the dereferenced int
    that is passed in as Param 4.
    Polling using this message will result in the Intel&reg; QuickAssist Technology
    OpenSSL\* Engine being notified when instances of an acceleration device go
    offline or come back online. By sending this message more frequently you can
    decrease the time taken for the engine to become aware of instances going
    offline/coming back online at the expense of additional cpu cycles. The
    suggested polling interval would be around 0.5 seconds to 1 second. This
    message may be sent at any time after engine initialization. This message
    is not supported in the FreeBSD operating system or in the qatlib RPM.

Message String: DISABLE_QAT_OFFLOAD
Param 3:        0
Param 4:        NULL
Description:
    This message is used to disable offload of crypto operations to the
    acceleration devices when QAT Offload is enabled, with the immediate effect
    that these operations are performed on-core instead.
    This message may be sent at any time after engine initialization.

Intel® QuickAssist Technology OpenSSL* Engine Build Options

The following is a list of the options that can be used with the ./configure command when building the Intel® QAT OpenSSL* Engine:

Mandatory (when building against QAT Driver HW version 1.7 package)

--with-qat_dir=/path/to/qat_driver
    Specify the path to the source code of the Intel(R) QAT Driver. This path
    is needed for compilation in order to locate the Intel(R) QAT header files.
    For example if using Intel&reg; QAT Driver HW version 1.7 package that was
    unpacked to `/QAT`, and you are using an Intel(R) Communications Chipset
    C62X Series device then you would use the following setting:
    --with-qat_dir=/QAT
    This option is not needed if you are building against the in-tree driver
    installed via qatlib RPM. Also, if use of Multi-buffer Software optimization
    over QAT is preferred, then this option is not needed.

Mandatory (when building against OpenSSL from source)

--with-openssl_install_dir=/path/to/openssl_install
    Specify the path to the top level where the OpenSSL* build was installed to.
    If this path is specified then qatengine.so engine library will be copied
    into the folder containing the other dynamic engines when you run
    'make install'. This option, if not specified uses system OpenSSL if the
    version is 1.1.1 and installs qatengine.so in the system enginesdir
    (eg: /usr/lib64/engine-1.1). OpenSSL library and devel package needs to be
    installed and should be version 1.1.1 series if this option is not specified.
    For example if you installed OpenSSL* to its default location of
    `/usr/local/ssl` then you would use the following setting:
    --with-openssl_install_dir=/usr/local/ssl

Mandatory (when building against OpenSSL 1.1.0)

--with-openssl_dir=/path/to/openssl
    Specify the path to the top level of the OpenSSL* source code.  This path
    is only needed to regenerate engine specific error source files using the
    mkerr.pl script from the OpenSSL source files. This option needs to be used
    if there is any new error message added in the QAT Engine source files
    and the error files will get updated using the mkerr.pl script. The default
    if not provided will build QAT Engine from the existing error files
    e_qat_err.c, e_qat_err.h & e_qat.txt in the QAT Engine dir which is
    generated from OpenSSL release mentioned in the github release page.
    This option is mandatory when building against OpenSSL* 1.1.0 as existing
    err files is generated for 1.1.1 which is not compatible for 1.1.0 and
    `--with-openssl_install_dir` needs to be provided to regenerate it.
    For example if you cloned the OpenSSL* Github* repository from within `/`
    then you would use the following setting:
    --with-openssl_dir=/openssl

Mandatory (when using the Intel&reg; Crypto Multi-buffer Library)

--enable-multibuff_offload/--disable-multibuff_offload
    Enable/Disable Intel(R) Multi-buffer offload feature. This flag needs to be
    enabled if Multi-buffer based software optimizations need to be used. This
    flag when enabled uses Intel&reg; Crypto Multi-buffer library and includes
    from the default path (/usr/local). If the crypto_mb library is installed
    in a path other than the default then --with-multibuff_install_dir needs
    to be set to the path where it is installed (disabled by default).

Mandatory (when using the Intel&reg; Multi-Buffer Crypto for IPsec Library)

--enable-ipsec_offload/--disable-ipsec_offload
    Enable/Disable Intel(R) IPsec offload. This flag needs to be enabled if
    IPsec based software optimizations needs to be used. This flag when enabled
    uses Intel&reg; IPsec library and headers from the default path (/usr).
    If the Intel&reg; IPsec library is installed in the path other than the
    default then `--with-ipsec_install_dir` needs to be set with the path where
    its installed (disabled by default).

Mandatory (When both QAT and Multi-buffer capabilties are present in the system
and use of Multi-buffer optimization over QAT is preferred)

--disable-qat_offload
    Disable Intel(R) QAT Hardware offload. This flag needs to be enabled if
    the system has both QAT Hardware and Multi-buffer Software optimization
    capabilities and the in-tree driver is installed in the system via `qatlib`
    RPM and use of Multi-buffer optimization over QAT is prefered. Incase of
    the in-tree driver eventhough Multi-buffer optimization is enabled via
    use of the `--enable-multibuff_offload` option, if both capabilities are
    available (both QAT offload or Multi-buffer offload) then QAT offload will
    be used by default. However, use of this --disable-qat_offload option will
    force the use of Multi-buffer optimization.

Optional

--with-qat_install_dir=/path/to/qat_driver/build
    Specify the path to the location of the built Intel(R) QAT Driver library
    files. This path is needed in order to link to the userspace libraries of
    the Intel(R) QAT Driver.
    The default if not specified is to use the path specified by --with-qat_dir
    with '/build' appended.  You only need to specify this parameter if the
    driver library files have been built somewhere other than the default.

--with-multibuff_install_dir=/path/to/ipp-crypto_Multi-buffer_build
    Specify the path of the built Intel(R) Crypto Multi-buffer library.
    This path is needed in order to link to the Crypto Multi-buffer library.
    The default if not specified is to use the standard installation path which
    is '/usr/local'. You only need to specify this parameter if the ipp-crypto
    Multi-buffer library files have been built somewhere other than the default.

--with-ipsec_install_dir=/path/to/intel-ipsec_mb_build
    Specify the path of the built Intel(R) IPsec library. This path
    is needed in order to link to the Intel(R) IPsec library.
    The default if not specified is to use the standard installation path
    which is '/usr'. You only need to specify this parameter if the
    Intel&reg; IPsec library files have been built somewhere other than the
    default.

--enable-qat_contig_mem/--disable-qat_contig_mem
    Enable/Disable compiling against the qat_contig_mem driver supplied within
    QAT Engine instead of the USDM component distributed with the Intel(R) QAT
    Driver HW Version 1.7 (disabled by default).

--with-usdm_dir=/path/to/usdm/directory
    Specify the path to the location of the USDM component.
    The default if not specified is to use the path specified by --with-qat_dir
    with '/quickassist/utilities/libusdm_drv' appended.  You only need to
    specify this parameter if using the USDM component, and if the path to it
    is different from the default.

--disable-qat_rsa/--enable-qat_rsa
    Disable/Enable Intel(R) QAT RSA offload (enabled by default)

--disable-qat_dsa/--enable-qat_dsa
    Disable/Enable Intel(R) QAT DSA offload (enabled by default)

--disable-qat_dh/--enable-qat_dh
    Disable/Enable Intel(R) QAT DH offload (enabled by default)

--disable-qat_ecdh/--enable-qat_ecdh
    Disable/Enable Intel(R) QAT ECDH offload (enabled by default)

--disable-qat_ecdsa/--enable-qat_ecdsa
    Disable/Enable Intel(R) QAT ECDSA offload (enabled by default)

--disable-qat_ciphers/--enable-qat_ciphers
    Disable/Enable Intel(R) QAT Chained Cipher offload (enabled by default)

--disable-qat_prf/--enable-qat_prf
    Disable/Enable Intel(R) QAT PRF offload (enabled by default)

--disable-qat_hkdf/--enable-qat_hkdf
    Disable/Enable Intel(R) QAT HKDF offload (disabled by default)

--disable-qat_ecx/--enable-qat_ecx
    Disable/Enable Intel(R) QAT X25519/X448 offload (enabled by default)

--disable-vaes_gcm/--enable-vaes_gcm
    Disable/Enable Intel(R) IPsec Vectorized AES-GCM offload.
    This flag is valid only when Intel(R) IPsec support is enabled using the
    flag --enable-ipsec_offload (enabled by default if ipsec_offload is enabled).

--disable-multibuff_rsa/--enable-multibuff_rsa
    Disable/Enable Intel(R) Multibuff RSA offload. This flag is valid only
    when Multi-buffer support is enabled using the flag --enable-multibuff_offload
    (enabled by default if multibuff_offload is enabled).

--disable-multibuff_ecx/--enable-multibuff_ecx
    Disable/Enable Intel(R) Multibuff X25519 offload. This flag is valid only
    when Multi-buffer support is enabled using the flag --enable-multibuff_offload
    (enabled by default if multibuff_offload is enabled).

--disable-qat_small_pkt_offload/--enable-qat_small_pkt_offload
    Enable the offload of small packet cipher operations to Intel(R) QAT. When
    disabled, these operations are performed using the CPU (disabled by
    default).

--disable-qat_warnings/--enable-qat_warnings
    Disable/Enable warnings to aid debugging. Warning: This option should never
    be left on in a production environment as it may introduce side channel
    timing attack vulnerabilities (disabled by default).

--disable-qat_debug/--enable-qat_debug
    Disable/Enable debug output to aid debugging. This will also enable the
    warning messages above. Warning: This option should never be enabled in a
    production environment as it may output private key information to the
    console/logs and may also introduce side channel timing attack
    vulnerabilities (disabled by default).

--disable-qat_mem_warnings/--enable-qat_mem_warnings
    Disable/Enable warnings from the userspace memory management code to aid
    debugging. Warning: This option should never be left on in a production
    environment as it may introduce side channel timing attack vulnerabilities
    (disabled by default).

--disable-qat_mem_debug/--enable-qat_mem_debug
    Disable/Enable debug output from the userspace memory management code to
    aid debugging. This will also enable the warning messages above. This
    option produces quite verbose output hence why it is separate to the
    standard debug. Warning: This option should never be enabled in a
    production environment as it may output private key information to the
    console/logs and may also introduce side channel timing attack
    vulnerabilities (disabled by default).

--with-qat_debug_file=/file/and/path/to/log/qat/debug/to
    This option turns on logging to a file instead of to stderr. It works with
    any combination of the following flags:
      --enable-qat_warnings
      --enable-qat_debug
      --enable-qat_mem_warnings
      --enable-qat_mem_debug
    The option should specify the full absolute path and filename that you would
    like to log to. The directory needs to be writable by the user the process
    is running as, and the log file can get very big, very quickly.
    The existing log file will be replaced rather than appended to on each run
    of the application. If the file cannot be opened for writing then the
    logging will default to output to stderr.
    As with the other logging options this option should never be enabled in a
    production environment as private key information and plaintext data will
    be logged to the file (logging to file is disabled by default).

--with-engine_id="<engine_id>"
   This option needs to be specified if you want to use an engine id other than
   the default which is now "qatengine" (previously it was "qat"). This option
   can be used to set engine id as "qat" for application that still uses older
   engine id within the application. Additionally, qatengine library name in the
   OpenSSL engine install dir has to be renamed with the engine_id provided here
   (disabled by default).

--disable-multi_thread/--enable-multi_thread
    Disable/Enable an alternative way of managing within userspace the pinned
    contiguous memory allocated by the qat_contig_mem driver. This alternative
    method will give improved performance in a multi-threaded environment by
    making the slab pools thread local to avoid locking between threads.
    Although this can give better performance there are several drawbacks such
    as the memory slabs will be utilized less efficiently, and you cannot
    allocate in one thread and free in another thread.  Running in this mode
    also does not support processes that fork (disabled by default).

--disable-qat_lenstra_protection/--enable-qat_lenstra_protection
    Disable/Enable protection against Lenstra attack (CVE-2017-5681)
    (protection is enabled by default). The RSA-CRT implementation in the
    Intel(R) QAT OpenSSL* Engine, for OpenSSL* versions prior to v0.5.19,
    may allow remote attackers to obtain private RSA keys by conducting a
    Lenstra side-channel attack.  From version v0.5.19 onward, protection
    against this form of attack is effected by performing a Verify/Encrypt
    operation after the Sign/Decrypt operation, and if a failure is detected
    then re-running the Sign/Decrypt operation using the CPU.
    However, future releases of Intel(R) QAT driver code or firmware may
    effect this protection instead, in which case the Intel(R) QAT OpenSSL*
    Engine code-based protection would no longer be required and this
    configuration option should then be selected.
    For further information, please refer to:-
    https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00071&languageid=en-fr
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5681

--disable-qat_auto_engine_init_on_fork/--enable-qat_auto_engine_init_on_fork
    Disable/Enable the engine from being initialized automatically following a
    fork operation. This is useful in a situation where you want to tightly
    control how many instances are being used for processes. For instance if an
    application forks to start a process that does not utilize QAT currently
    the default behaviour is for the engine to still automatically get started
    in the child using up an engine instance. After using this flag either the
    engine needs to be initialized manually using the engine message:
    INIT_ENGINE or will automatically get initialized on the first QAT crypto
    operation. The initialization on fork is enabled by default.

--enable-multibuff_heuristic_timeout/--disable-multibuff_heuristic_timeout
    Disable/Enable self tuning of the timeout in the polling thread in the
    Intel(R) Multi-buffer offload. This flag is valid only
    incase of Multi-buffer offload (disabled by default).

--disable-qat_cycle_counts/--enable-qat_cycle_counts
    Disable/Enable cycle count measurement in the Intel(R) Multi-buffer offload.
    This support is only extended to Multi-buffer offload code path
    (disabled by default).

--with-cc-opt="parameters"
    Sets additional parameters that will be added to the CFLAGS variable at
    compile time.

--with-ld-opt="parameters"
    Sets additional parameters that will be used during linking.

Using the OpenSSL* Configuration File to Load/Initialize Engines

OpenSSL* includes support for loading and initializing engines via the openssl.cnf file. The openssl.cnf file is contained in the ssl subdirectory of the path you install OpenSSL* to. By default OpenSSL* does not load the openssl.cnf file at initialization time. In order to load the file you need to make the following function call from your application as the first call to the OpenSSL* library:

OPENSSL_init_crypto(OPENSSL_INIT_LOAD_CONFIG, NULL);

The second parameter determines the name of the section containing the application specific initialization settings. If you set the parameter to NULL as in the example above it will default to look for the openssl_conf section. If you want to use your own section you should declare a structure of type OPENSSL_INIT_SETTINGS and set the appname field to a string containing the section name you wish to use. The example config file sections below assume you are using the default openssl_conf section name.

If converting an existing application to use the Intel® QAT OpenSSL* Engine you may find that the application instead makes the now deprecated call to:

OPENSSL_config(NULL);

Where the parameter is a const char* pointer to the appname section you want to use, or NULL to use the default openssl_conf section.

Currently this will give the same behaviour as the OPENSSL_init_crypto(OPENSSL_INIT_LOAD_CONFIG, NULL) call but as it is deprecated it should not be relied upon for future use.

For further details on using the OPENSSL_init_crypto function please see the OpenSSL* online documentation located at: https://www.openssl.org/docs/man1.1.0/crypto/OPENSSL_init_crypto.html

In order to start using the openssl.cnf file it needs some additional lines adding. You should add the following statement in the global section (this is the section before the first bracketed section header):

openssl_conf = openssl_init

The string openssl_init is the name of the section in the configuration file which describes the application specific settings. You do not need to stick to the naming convention here if you prefer to use a different name.

The openssl_init section can be located at the end of the global section (as the first bracketed section), or further down the configuration file. It should have the following added:

[ openssl_init ]
engines = engine_section

The engines string is a keyword that OpenSSL* recognises as a configuration module. It should be set to a string which is the section name containing a list of the engines to be loaded. So for the Intel® QAT OpenSSL* Engine the section should contain:

[ engine_section ]
qat = qat_section

The qat_section contains all the settings relating to that particular engine. For instance it may contain:

[ qat_section ]
engine_id = qatengine
dynamic_path = /usr/local/ssl/lib/engines-1.1/qatengine.so
# Add engine specific messages here
default_algorithms = ALL

Where engine_id specifies the name of engine to load (should be qatengine).

Where dynamic_path is the location of the loadable shared library implementing the engine. There is no need to specify this line if the engine is located within the standard path that OpenSSL* was installed to.

Where default_algorithms specifies which algorithms supplied by the engine should be used by default. Specify ALL to make all algorithms supplied by the engine be used by default.

In addition the qat_section may contain settings that call custom engine specific messages. For instance:

ENABLE_EVENT_DRIVEN_MODE = EMPTY

is functionally equivalent of making the following engine specific message function call:

ENGINE_ctrl_cmd(e, "ENABLE_EVENT_DRIVEN_MODE", 0, NULL, NULL, 0);

You should set the setting to EMPTY if there are no parameters to pass, or assign the value that would be passed as the 4th parameter of the equivalent ENGINE_ctrl_cmd call. It should be noted that this mechanism is only useful for passing simple values at engine initialization time. You cannot pass 3rd parameter values, pass complex structures or deal with return values via this mechanism.

Engine specific messages should be specified before the default_algorithms setting or incorrect behaviour may result. The following messages are supported:

  • ENABLE_EVENT_DRIVEN_POLLING_MODE
  • ENABLE_EXTERNAL_POLLING
  • ENABLE_INLINE_POLLING
  • ENABLE_SW_FALLBACK
  • SET_INTERNAL_POLL_INTERVAL
  • SET_EPOLL_TIMEOUT
  • SET_MAX_RETRY_COUNT

In case of forking, the custom values are inherited by the child process.

By default the engine will get initialized at the end of this section (after all the custom engine specific messages have been sent). This can be controlled via an additional init setting that is out of scope of the documentation here.

For further details on using the OpenSSL* configuration file please see the OpenSSL* online documentation located at: https://www.openssl.org/docs/man1.1.0/apps/config.html

By setting up the configuration file as above it is possible for instance to run the OpenSSL* speed application to use the Intel® QAT OpenSSL* Engine without needing to specify -engine qatengine as a command line option.

Using the OpenSSL* Pipelining Capability

The OpenSSL* pipelining feature provides the capability to parallelise the processing for a single connection. For example a big buffer to be encrypted can be split into smaller chunks with each chunk encrypted simultaneously using pipelining. The Intel® QAT OpenSSL* Engine supports OpenSSL* pipelining capability for chained cipher encryption operations only. The engine provides a maximum of 32 pipelines (buffer chunks) with a maximum size of 16,384 bytes for each pipeline. When pipelines are used, they are always offloaded to the accelerator ignoring the small packet offload threshold. Please refer to the OpenSSL* manual for more information about pipelining. https://www.openssl.org/docs/man1.1.0/ssl/SSL_CTX_set_split_send_fragment.html

Using the OpenSSL* asynchronous mode 'ASYNC_JOB' infrastructure

Asynchronous operation utilizes the OpenSSL* asychronous mode (ASYNC_JOB infrastructure) introduced in OpenSSL* version 1.1.0. In the OpenSSL* master branch this infrastructure was augmented to provide an additional callback method by which the OpenSSL* Engine can be notified of crypto operation request completions by the hardware accelerator. This additional method can be used if you think that using the alternative file descriptor method descriptor is too costly in terms of CPU cycles or in some context where a file descriptor is not appropriate.

The QAT OpenSSL* Engine build system will automatically detect whether the OpenSSL* version being built against supports this additional callback method. If so, the QAT OpenSSL* Engine code will use the callback mechanism for job completion rather than the file descriptor mechanism if a callback function has been set. If a callback has not been set then the file descriptor method will be used.

For further details on using the OpenSSL* asynchronous mode infrastructure please see the OpenSSL* online documentation located at: https://www.openssl.org/docs/manmaster/man3/ASYNC_start_job.html

with additional information at: https://www.openssl.org/docs/manmaster/man3/ASYNC_WAIT_CTX_new.html.

Functionality of the Intel® QAT OpenSSL* Engine Software Fallback Feature

Requirements:

  1. This Intel® QAT OpenSSL* Engine supports the Intel® QAT Driver Heartbeat feature only from version 4.6 of the following device:

Note: Heartbeat feature support currently does not extend to Symmetric Chained Cipher Offload, PRF, HKDF & X25519/X448 offload. The heartbeat feature is also not available when running under the FreeBSD operating system or in the qatlib RPM.

  1. Intel® QAT OpenSSL* Engine needs to be configured to disable Symmetric Chained Cipher Offload, HKDF & X25519/X448 offload by adding the below four flags in the configure command of Intel® QAT OpenSSL* Engine build.
--disable-qat_ciphers --disable-qat_prf --disable-qat_hkdf --disable-qat_ecx

Information on this Heartbeat feature can be found in: Intel® QuickAssist Technology Software for Linux* - Programmer's Guide - HW version 1.7 (336210) - Section 3.17 Heartbeat.

This document can be found on the 01.org website at the following hyperlink:

The Intel® QuickAssist Heartbeat feature provides a mechanism for the Intel® QAT OpenSSL* Engine to detect unresponsive acceleration devices and to be notified of the start and end of any reset of the acceleration devices. The Heartbeat feature suspends all QAT instances associated with that acceleration device between these two reset-start and reset-end events. An acceleration device can be configured for automatic reset by the QAT framework upon heartbeat failure by using the AutoResetOnError = 1 field in the [GENERAL] section of device configuration file /etc/<device>.conf. The Intel® QAT OpenSSL* Engine's software fallback feature requires this field to be set.

The Intel® QAT OpenSSL* Engine's software fallback feature, when enabled by the user, essentially provides continuity of crypto operations for the application between the two above-mentioned reset-start & reset-end events. It does this by exhibiting the following behaviour:

  • Any requests that have already been submitted to the acceleration device that goes down but have not completed will be handled as on core requests and will complete.
  • Any new requests coming in while the acceleration device is offline will either be submitted to the other acceleration devices (if any are available) or if none are available then the request will be handled on core.
  • Once the acceleration device has come back online new requests will be able to use instances from that acceleration device again.

This should all happen in a transparent way with the only noticeable effects being a slow down in performance until the acceleration device comes back online. The Heartbeat feature is not supported in the FreeBSD operating system or in the qatlib RPM.

Intel® QAT OpenSSL* Engine HKDF Support

The HKDF support in the Intel® QAT OpenSSL* Engine is available only from Version 4.8 of Intel® QuickAssist Technology Driver for Linux HW Version 1.7. By default this support is disabled as it is added as an experimental feature. It can be enabled using the flag --enable-qat_hkdf in the configure command combined with modifying the Intel® QuickAssist Technology Driver file's config variable 'ServicesProfile' from its default value of 'DEFAULT' to 'CRYPTO'.

Intel® QAT OpenSSL* Engine Multi-buffer Support

This Intel® QAT OpenSSL* Engine supports Multi-buffer based software optimizations for RSA and X25519 using the Intel® Crypto Multi-buffer library based on Intel® AVX-512 Integer Fused Multiply Add (IFMA) operations.

The Intel® QAT OpenSSL* Engine Multi-buffer Support, when enabled by the user using the build instructions mentioned below performs operation by batching up multiple requests maintained in queues and uses the OpenSSL asynchronous infrastructure to submit the batched requests upto 8 to Crypto Multi-buffer API which processes them in parallel using AVX512 vector instructions. Multi-buffer optimizations will be beneficial to use in asynchronous operations where there are many parallel connections.

Requirements

Successful operation of the Multi-buffer Software optmization requires a software tool chain that supports OpenSSL* 1.1.1 and Intel® Crypto Multi-buffer library cloned from the ipp-crypto release version IPP Crypto 2020 Update 3. The crypto_mb library needs to be installed using the instructions in the Readme from Crypto Multi-buffer Library. This support is not available in the FreeBSD operating system.

Build Instructions for Intel® QAT OpenSSL* Engine to enable Multi-buffer Support

The following example is assuming:

  • The Intel® QAT OpenSSL* Engine was cloned to its own location at the root of the drive: /.
  • The Intel® Crypto Multi-buffer library was installed to the default path (/usr/local).
  • Prebuilt OpenSSL* 1.1.1 from the system is used.

To build and install the Intel® QAT OpenSSL* Engine with Multi-buffer offload:

cd /QAT_Engine
./autogen.sh
./configure --enable-multibuff_offload
make
make install

Testing with OpenSSL Speed

cd /path/to/openssl_install/bin

* RSA 2K
    ./openssl speed -engine qatengine -elapsed -async_jobs 8 rsa2048
* ECDH X25519
    ./openssl speed -engine qatengine -elapsed -async_jobs 8 ecdhx25519

Intel® QAT OpenSSL* Engine IPsec Vectorized AES Support

This Intel® QAT OpenSSL* Engine supports software based optimizations for AES-GCM using the Intel® Multi-Buffer Crypto for IPsec Library.

The Intel® QAT OpenSSL* Engine IPsec VAES support, when enabled by the user using the build instructions mentioned below performs operation by submitting requests synchronously with IPsec API which accelarates using the vectorized AES and AVX512 instructions from the processor.

Requirements

Successful operation of the IPsec offload requires a software tool chain that supports OpenSSL* 1.1.1 and Intel® Multi-Buffer crypto for IPsec Library release version v0.55 cloned from the intel-ipsec-mb repo and installed using the instructions from the intel-ipsec README. This support is not tested in the FreeBSD operating system.

Build flag to enable Intel® IPsec Vectorized AES Support

This support can be enabled using the flag --enable-ipsec_offload along with other flags for QAT and Multibuff offload in the configure command.

Testing with OpenSSL Speed

cd /path/to/openssl_install/bin

*AES-128-GCM
    ./openssl speed -engine qatengine -elapsed -evp aes-128-gcm
*AES-192-GCM
    ./openssl speed -engine qatengine -elapsed -evp aes-192-gcm
*AES-256-GCM
    ./openssl speed -engine qatengine -elapsed -evp aes-256-gcm

Legal

Intel, Intel Atom, and Xeon are trademarks of Intel Corporation in the U.S. and/or other countries.

*Other names and brands may be claimed as the property of others.

Copyright © 2016-2020, Intel Corporation. All rights reserved.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].