summaryrefslogtreecommitdiffstats
path: root/test/test_memif.py
AgeCommit message (Expand)AuthorFilesLines
2022-11-09tests: initial asf framework refactoring for 'make test'Pratikshya Prasai1-1/+1
2022-09-27tests: disable failing tests on ubuntu-22.04 debian-11Dave Wallace1-1/+5
2022-05-10tests: replace pycodestyle with blackKlement Sekera1-71/+70
2022-02-17tests: make tests less make dependentKlement Sekera1-1/+1
2021-11-09memif: memif linkstate can't become upDaniel Béreš1-0/+40
2021-05-13tests: move test source to vpp/testDave Wallace1-0/+308
2019-08-22tests: move plugin tests to src/plugins/*/testDave Wallace1-275/+0
2019-08-20api: Cleanup APIs interface.apiJakub Grajciar1-3/+3
2019-06-26tests: fix test-checkstyle failure in test_memif.pyPaul Vinciguerra1-2/+2
2019-06-26tests: fix memif testsJakub Grajciar1-3/+7
2019-06-18fib: fib api updatesNeale Ranns1-7/+6
2019-03-15Revert "API: Cleanup APIs interface.api"Ole Trøan1-7/+6
2019-03-15API: Cleanup APIs interface.apiJakub Grajciar1-6/+7
2019-03-11vpp_papi_provider: Remove more wrapper functions.Ole Troan1-2/+3
2019-03-11VPP-1508: Tests: Fix vpp_api struct.error under py3.Paul Vinciguerra1-12/+19
2019-03-01Tests: Remove all wildcard imports.Paul Vinciguerra1-1/+3
2018-10-10Test FW: Use unittest temp dir as unix runtime dirJakub Grajciar1-21/+24
2018-09-27memif: Memif Test CaseJakub Grajciar1-0/+259
nough Cryptodev resources for all workers, the node graph is reconfigured by adding and changing the default next nodes. The following nodes are added: * dpdk-crypto-input : polling input node, dequeuing from crypto devices. * dpdk-esp-encrypt : internal node. * dpdk-esp-decrypt : internal node. * dpdk-esp-encrypt-post : internal node. * dpdk-esp-decrypt-post : internal node. Set new default next nodes: * for esp encryption: esp-encrypt -> dpdk-esp-encrypt * for esp decryption: esp-decrypt -> dpdk-esp-decrypt ### How to enable VPP IPSec with DPDK Cryptodev support When building DPDK with VPP, Cryptodev support is always enabled. Additionally, on x86_64 platforms, DPDK is built with SW crypto support. ### Crypto Resources allocation VPP allocates crypto resources based on a best effort approach: * first allocate Hardware crypto resources, then Software. * if there are not enough crypto resources for all workers, the graph node is not modified and the default VPP IPsec implementation based in OpenSSL is used. The following message is displayed: 0: dpdk_ipsec_init: not enough Cryptodevs, default to OpenSSL IPsec ### Configuration example To enable DPDK Cryptodev the user just need to provide cryptodevs in the startup.conf. Below is an example startup.conf, it is not meant to be a default configuration: ``` dpdk { dev 0000:81:00.0 dev 0000:81:00.1 dev 0000:85:01.0 dev 0000:85:01.1 vdev crypto_aesni_mb0,socket_id=1 vdev crypto_aesni_mb1,socket_id=1 } ``` In the above configuration: * 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) ### Operational data The following CLI command displays the Cryptodev/Worker mapping: show crypto device mapping [verbose] ### nasm Building the DPDK Crypto Libraries requires the open source project nasm (The Netwide Assembler) to be installed. Recommended version of nasm is 2.12.02. Minimum supported version of nasm is 2.11.06. Use the following command to determine the current nasm version: nasm -v CentOS 7.3 and earlier and Fedora 21 and earlier use unsupported versions of nasm. Use the following set of commands to build a supported version: wget http://www.nasm.us/pub/nasm/releasebuilds/2.12.02/nasm-2.12.02.tar.bz2 tar -xjvf nasm-2.12.02.tar.bz2 cd nasm-2.12.02/ ./configure make sudo make install