summaryrefslogtreecommitdiffstats
path: root/src
diff options
context:
space:
mode:
authorSergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>2017-08-31 15:12:00 +0100
committerFlorin Coras <florin.coras@gmail.com>2017-08-31 21:40:18 +0000
commit324ad39c1d006122f4b08e8deea560e6be64937a (patch)
treed81e7b08fbb49c42d42d1498e6e4b0f0ada588ca /src
parent49a04b9545de22beaef5218d3985896d6ba37982 (diff)
dpdk/ipsec: update doc regarding startup.conf
Change-Id: Ie449072ab1efec081235b508f1def60a1287ff5f Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
Diffstat (limited to 'src')
-rw-r--r--src/plugins/dpdk/ipsec/dpdk_crypto_ipsec_doc.md17
1 files changed, 7 insertions, 10 deletions
diff --git a/src/plugins/dpdk/ipsec/dpdk_crypto_ipsec_doc.md b/src/plugins/dpdk/ipsec/dpdk_crypto_ipsec_doc.md
index b3dbd6ea025..8ea77a6c30c 100644
--- a/src/plugins/dpdk/ipsec/dpdk_crypto_ipsec_doc.md
+++ b/src/plugins/dpdk/ipsec/dpdk_crypto_ipsec_doc.md
@@ -39,28 +39,25 @@ VPP allocates crypto resources based on a best effort approach:
### Configuration example
-To enable DPDK Cryptodev the user just need to provide cryptodevs int the
-startup.conf.
+To enable DPDK Cryptodev the user just need to provide cryptodevs in the startup.conf.
-Example startup.conf:
+Below is an example startup.conf, it is not meant to be a default configuration:
```
dpdk {
- socket-mem 1024,1024
- num-mbufs 131072
dev 0000:81:00.0
dev 0000:81:00.1
- enable-cryptodev
dev 0000:85:01.0
dev 0000:85:01.1
- vdev cryptodev_aesni_mb_pmd,socket_id=1
- vdev cryptodev_aesni_mb_pmd,socket_id=1
+ vdev crypto_aesni_mb0,socket_id=1
+ vdev crypto_aesni_mb1,socket_id=1
}
```
In the above configuration:
-* 0000:85:01.0 and 0000:85:01.1 are crypto BDFs and they require the same driver binding as DPDK Ethernet devices but they do not support any extra configuration options.
-* Two AESNI-MB Software Cryptodev PMDs are created in NUMA node 1.
+* 0000:81:01.0 and 0000:81:01.1 are Ethernet device BDFs.
+* 0000:85:01.0 and 0000:85:01.1 are Crypto device BDFs and they require the same driver binding as DPDK Ethernet devices but they do not support any extra configuration options.
+* Two AESNI-MB Software (Virtual) Cryptodev PMDs are created in NUMA node 1.
For further details refer to [DPDK Crypto Device Driver documentation](http://dpdk.org/doc/guides/cryptodevs/index.html)