git.droids-corp.org
/
dpdk.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
maintainers: add Windows exports script
[dpdk.git]
/
doc
/
guides
/
cryptodevs
/
aesni_mb.rst
diff --git
a/doc/guides/cryptodevs/aesni_mb.rst
b/doc/guides/cryptodevs/aesni_mb.rst
index
3950daa
..
1eff2b0
100644
(file)
--- a/
doc/guides/cryptodevs/aesni_mb.rst
+++ b/
doc/guides/cryptodevs/aesni_mb.rst
@@
-1,5
+1,5
@@
.. SPDX-License-Identifier: BSD-3-Clause
.. SPDX-License-Identifier: BSD-3-Clause
- Copyright(c) 2015-201
7
Intel Corporation.
+ Copyright(c) 2015-201
8
Intel Corporation.
AESN-NI Multi Buffer Crypto Poll Mode Driver
============================================
AESN-NI Multi Buffer Crypto Poll Mode Driver
============================================
@@
-27,6
+27,7
@@
Cipher algorithms:
* RTE_CRYPTO_CIPHER_AES256_CTR
* RTE_CRYPTO_CIPHER_AES_DOCSISBPI
* RTE_CRYPTO_CIPHER_DES_CBC
* RTE_CRYPTO_CIPHER_AES256_CTR
* RTE_CRYPTO_CIPHER_AES_DOCSISBPI
* RTE_CRYPTO_CIPHER_DES_CBC
+* RTE_CRYPTO_CIPHER_3DES_CBC
* RTE_CRYPTO_CIPHER_DES_DOCSISBPI
Hash algorithms:
* RTE_CRYPTO_CIPHER_DES_DOCSISBPI
Hash algorithms:
@@
-38,16
+39,23
@@
Hash algorithms:
* RTE_CRYPTO_HASH_SHA384_HMAC
* RTE_CRYPTO_HASH_SHA512_HMAC
* RTE_CRYPTO_HASH_AES_XCBC_HMAC
* RTE_CRYPTO_HASH_SHA384_HMAC
* RTE_CRYPTO_HASH_SHA512_HMAC
* RTE_CRYPTO_HASH_AES_XCBC_HMAC
+* RTE_CRYPTO_HASH_AES_CMAC
+* RTE_CRYPTO_HASH_AES_GMAC
+* RTE_CRYPTO_HASH_SHA1
+* RTE_CRYPTO_HASH_SHA224
+* RTE_CRYPTO_HASH_SHA256
+* RTE_CRYPTO_HASH_SHA384
+* RTE_CRYPTO_HASH_SHA512
AEAD algorithms:
* RTE_CRYPTO_AEAD_AES_CCM
AEAD algorithms:
* RTE_CRYPTO_AEAD_AES_CCM
+* RTE_CRYPTO_AEAD_AES_GCM
Limitations
-----------
* Chained mbufs are not supported.
Limitations
-----------
* Chained mbufs are not supported.
-* Only in-place is currently supported (destination address is the same as source address).
Installation
Installation
@@
-56,12
+64,13
@@
Installation
To build DPDK with the AESNI_MB_PMD the user is required to download the multi-buffer
library from `here <https://github.com/01org/intel-ipsec-mb>`_
and compile it on their user system before building DPDK.
To build DPDK with the AESNI_MB_PMD the user is required to download the multi-buffer
library from `here <https://github.com/01org/intel-ipsec-mb>`_
and compile it on their user system before building DPDK.
-The latest version of the library supported by this PMD is v0.
48
, which
-can be downloaded from `<https://github.com/01org/intel-ipsec-mb/archive/v0.
48.zip>`_
.
+The latest version of the library supported by this PMD is v0.
52
, which
+can be downloaded from `<https://github.com/01org/intel-ipsec-mb/archive/v0.
52.zip>`
.
.. code-block:: console
.. code-block:: console
- make
+ make
+ make install
As a reference, the following table shows a mapping between the past DPDK versions
and the Multi-Buffer library version supported by them:
As a reference, the following table shows a mapping between the past DPDK versions
and the Multi-Buffer library version supported by them:
@@
-77,7
+86,9
@@
and the Multi-Buffer library version supported by them:
17.02 0.44
17.05 - 17.08 0.45 - 0.48
17.11 0.47 - 0.48
17.02 0.44
17.05 - 17.08 0.45 - 0.48
17.11 0.47 - 0.48
- 18.02+ 0.48
+ 18.02 0.48
+ 18.05 - 19.02 0.49 - 0.52
+ 19.05+ 0.52+
============== ============================
============== ============================
@@
-86,9
+97,6
@@
Initialization
In order to enable this virtual crypto PMD, user must:
In order to enable this virtual crypto PMD, user must:
-* Export the environmental variable AESNI_MULTI_BUFFER_LIB_PATH with the path where
- the library was extracted.
-
* Build the multi buffer library (explained in Installation section).
* Set CONFIG_RTE_LIBRTE_PMD_AESNI_MB=y in config/common_base.
* Build the multi buffer library (explained in Installation section).
* Set CONFIG_RTE_LIBRTE_PMD_AESNI_MB=y in config/common_base.
@@
-121,7
+129,7
@@
Extra notes
For AES Counter mode (AES-CTR), the library supports two different sizes for Initialization
Vector (IV):
For AES Counter mode (AES-CTR), the library supports two different sizes for Initialization
Vector (IV):
-* 12 bytes: used mainly for IP
S
ec, as it requires 12 bytes from the user, which internally
+* 12 bytes: used mainly for IP
s
ec, as it requires 12 bytes from the user, which internally
are appended the counter block (4 bytes), which is set to 1 for the first block
(no padding required from the user)
are appended the counter block (4 bytes), which is set to 1 for the first block
(no padding required from the user)