2 Copyright(c) 2015 Intel Corporation. All rights reserved.
4 Redistribution and use in source and binary forms, with or without
5 modification, are permitted provided that the following conditions
8 * Redistributions of source code must retain the above copyright
9 notice, this list of conditions and the following disclaimer.
10 * Redistributions in binary form must reproduce the above copyright
11 notice, this list of conditions and the following disclaimer in
12 the documentation and/or other materials provided with the
14 * Neither the name of Intel Corporation nor the names of its
15 contributors may be used to endorse or promote products derived
16 from this software without specific prior written permission.
18 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
19 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
20 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
21 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
22 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
23 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
24 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
25 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
26 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
27 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
28 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
30 AESN-NI Multi Buffer Crypto Poll Mode Driver
31 ============================================
34 The AESNI MB PMD (**librte_pmd_aesni_mb**) provides poll mode crypto driver
35 support for utilizing Intel multi buffer library, see the white paper
36 `Fast Multi-buffer IPsec Implementations on IntelĀ® Architecture Processors
37 <https://www-ssl.intel.com/content/www/us/en/intelligent-systems/intel-technology/fast-multi-buffer-ipsec-implementations-ia-processors-paper.html?wapkw=multi+buffer>`_.
39 The AES-NI MB PMD has current only been tested on Fedora 21 64-bit with gcc.
44 AESNI MB PMD has support for:
48 * RTE_CRYPTO_CIPHER_AES128_CBC
49 * RTE_CRYPTO_CIPHER_AES192_CBC
50 * RTE_CRYPTO_CIPHER_AES256_CBC
51 * RTE_CRYPTO_CIPHER_AES128_CTR
52 * RTE_CRYPTO_CIPHER_AES192_CTR
53 * RTE_CRYPTO_CIPHER_AES256_CTR
57 * RTE_CRYPTO_HASH_MD5_HMAC
58 * RTE_CRYPTO_HASH_SHA1_HMAC
59 * RTE_CRYPTO_HASH_SHA224_HMAC
60 * RTE_CRYPTO_HASH_SHA256_HMAC
61 * RTE_CRYPTO_HASH_SHA384_HMAC
62 * RTE_CRYPTO_HASH_SHA512_HMAC
63 * RTE_CRYPTO_HASH_AES_XCBC_HMAC
68 * Chained mbufs are not supported.
69 * Only in-place is currently supported (destination address is the same as source address).
70 * Only supports session-oriented API implementation (session-less APIs are not supported).
75 To build DPDK with the AESNI_MB_PMD the user is required to download the multi-buffer
76 library from `here <https://github.com/01org/intel-ipsec-mb>`_
77 and compile it on their user system before building DPDK.
78 The latest version of the library supported by this PMD is v0.45, which
79 can be downloaded in `<https://github.com/01org/intel-ipsec-mb/archive/v0.45.zip>`_.
81 .. code-block:: console
85 As a reference, the following table shows a mapping between the past DPDK versions
86 and the Multi-Buffer library version supported by them:
88 .. _table_aesni_mb_versions:
90 .. table:: DPDK and Multi-Buffer library version compatibility
92 ============= ============================
93 DPDK version Multi-buffer library version
94 ============= ============================
95 2.2 - 16.11 0.43 - 0.44
98 ============= ============================
104 In order to enable this virtual crypto PMD, user must:
106 * Export the environmental variable AESNI_MULTI_BUFFER_LIB_PATH with the path where
107 the library was extracted.
109 * Build the multi buffer library (explained in Installation section).
111 * Set CONFIG_RTE_LIBRTE_PMD_AESNI_MB=y in config/common_base.
113 To use the PMD in an application, user must:
115 * Call rte_eal_vdev_init("crypto_aesni_mb") within the application.
117 * Use --vdev="crypto_aesni_mb" in the EAL options, which will call rte_eal_vdev_init() internally.
119 The following parameters (all optional) can be provided in the previous two calls:
121 * socket_id: Specify the socket where the memory for the device is going to be allocated
122 (by default, socket_id will be the socket where the core that is creating the PMD is running on).
124 * max_nb_queue_pairs: Specify the maximum number of queue pairs in the device (8 by default).
126 * max_nb_sessions: Specify the maximum number of sessions that can be created (2048 by default).
130 .. code-block:: console
132 ./l2fwd-crypto -l 6 -n 4 --vdev="crypto_aesni_mb,socket_id=1,max_nb_sessions=128"