From 7fe90a66c718665e819ba68396e016ca51778d23 Mon Sep 17 00:00:00 2001 From: Pablo de Lara Date: Fri, 7 Jul 2017 05:36:56 +0100 Subject: [PATCH] doc: fix crypto scheduler command line examples Sample command lines for crypto scheduler were not correct, due to: - Typo in "crypto_scheduler" driver name - Multiple virtual devices require having unique names, driver name + a suffix, otherwise, just a single device is created. Fixes: d58a3f312545 ("crypto/scheduler: add documentation") Cc: stable@dpdk.org Signed-off-by: Pablo de Lara Acked-by: John McNamara --- doc/guides/cryptodevs/scheduler.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/guides/cryptodevs/scheduler.rst b/doc/guides/cryptodevs/scheduler.rst index be2eb0b633..f3ee88a93c 100644 --- a/doc/guides/cryptodevs/scheduler.rst +++ b/doc/guides/cryptodevs/scheduler.rst @@ -72,9 +72,9 @@ Initialization To use the PMD in an application, user must: -* Call rte_vdev_init("crpyto_scheduler") within the application. +* Call rte_vdev_init("crypto_scheduler") within the application. -* Use --vdev="crpyto_scheduler" in the EAL options, which will call +* Use --vdev="crypto_scheduler" in the EAL options, which will call rte_vdev_init() internally. @@ -106,7 +106,7 @@ Example: .. code-block:: console - ... --vdev "crypto_aesni_mb_pmd,name=aesni_mb_1" --vdev "crypto_aesni_mb_pmd,name=aesni_mb_2" --vdev "crypto_scheduler_pmd,slave=aesni_mb_1,slave=aesni_mb_2" ... + ... --vdev "crypto_aesni_mb0,name=aesni_mb_1" --vdev "crypto_aesni_mb1,name=aesni_mb_2" --vdev "crypto_scheduler,slave=aesni_mb_1,slave=aesni_mb_2" ... .. note:: -- 2.20.1