X-Git-Url: http://git.droids-corp.org/?a=blobdiff_plain;f=doc%2Fguides%2Fcryptodevs%2Fvirtio.rst;h=8b96446ff210cccc7decdb6c3d9ed961cf51651f;hb=19f3af2371a7fdc549cbc270c298be156b3bd545;hp=2c46bda866a14e49a483652bf333a78d8429eab5;hpb=582e9d7765f8d4823d2924572567f3e245b835b8;p=dpdk.git diff --git a/doc/guides/cryptodevs/virtio.rst b/doc/guides/cryptodevs/virtio.rst index 2c46bda866..8b96446ff2 100644 --- a/doc/guides/cryptodevs/virtio.rst +++ b/doc/guides/cryptodevs/virtio.rst @@ -63,7 +63,7 @@ QEMU can then be started using the following parameters: -device virtio-crypto-pci,id=crypto0,cryptodev=cryptodev0 [...] -Secondly bind the uio_generic driver for the virtio-crypto device. +Secondly bind the uio_pci_generic driver for the virtio-crypto device. For example, 0000:00:04.0 is the domain, bus, device and function number of the virtio-crypto device: @@ -83,27 +83,17 @@ The unit test cases can be tested as below: .. code-block:: console reserve enough huge pages - cd to the top-level DPDK directory - export RTE_TARGET=x86_64-native-linux-gcc - export RTE_SDK=`pwd` - cd to app/test - type the command "make" to compile - run the tests with "./test" - type the command "cryptodev_virtio_autotest" to test + cd to + meson test cryptodev_virtio_autotest The performance can be tested as below: .. code-block:: console reserve enough huge pages - cd to the top-level DPDK directory - export RTE_TARGET=x86_64-native-linux-gcc - export RTE_SDK=`pwd` - cd to app/test-crypto-perf - type the command "make" to compile - run the tests with the following command: - - ./dpdk-test-crypto-perf -l 0,1 -- --devtype crypto_virtio \ + cd to + + ./app/dpdk-test-crypto-perf -l 0,1 -- --devtype crypto_virtio \ --ptest throughput --optype cipher-then-auth --cipher-algo aes-cbc \ --cipher-op encrypt --cipher-key-sz 16 --auth-algo sha1-hmac \ --auth-op generate --auth-key-sz 64 --digest-sz 12 \