* [dpdk-stable] [PATCH v2] doc: update multiple instance info for NULL crypto
[not found] <1517841119-9277-1-git-send-email-vipin.varghese@intel.com>
@ 2018-02-06 13:43 ` Vipin Varghese
2018-02-06 16:11 ` [dpdk-stable] [PATCH v3] doc: add info on multiple instance SW crypto Vipin Varghese
0 siblings, 1 reply; 2+ messages in thread
From: Vipin Varghese @ 2018-02-06 13:43 UTC (permalink / raw)
To: dev
Cc: stable, pablo.de.lara.guarch, john.mcnamara, marko.kovacevic,
Vipin Varghese
Add foot note & example to inform user how to use multiple instance.
Signed-off-by: Vipin Varghese <vipin.varghese@intel.com>
---
V2 Changes:
- Updated Note for better wording - Pablo
- Multiple instance information to Crypto Device Lib - Pablo
---
doc/guides/cryptodevs/null.rst | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/doc/guides/cryptodevs/null.rst b/doc/guides/cryptodevs/null.rst
index 03a3ddc..f476e9d 100644
--- a/doc/guides/cryptodevs/null.rst
+++ b/doc/guides/cryptodevs/null.rst
@@ -41,6 +41,10 @@ each mbuf in the burst will be enqueued in an internal buffer for collection on
a dequeue call as long as the mbuf has a valid rte_mbuf_offload operation with
a valid rte_cryptodev_session or rte_crypto_xform chain of operations.
+.. Note::
+
+ In case of multiple NULL cryptos PMD instances, each should have unique id.
+
Features
--------
@@ -91,7 +95,9 @@ The following parameters (all optional) can be provided in the previous two call
Example:
-.. code-block:: console
+-.. code-block:: console
+
+ ./l2fwd-crypto -l 1 -n 4 \
+ --vdev="crypto_null,socket_id=0,max_nb_sessions=128" \
+ -- -p 1 --cdev SW --chain CIPHER_ONLY --cipher_algo "null"
- ./l2fwd-crypto -l 1 -n 4 --vdev="crypto_null,socket_id=0,max_nb_sessions=128" \
- -- -p 1 --cdev SW --chain CIPHER_ONLY --cipher_algo "null"
--
1.9.1
^ permalink raw reply [flat|nested] 2+ messages in thread
* [dpdk-stable] [PATCH v3] doc: add info on multiple instance SW crypto
2018-02-06 13:43 ` [dpdk-stable] [PATCH v2] doc: update multiple instance info for NULL crypto Vipin Varghese
@ 2018-02-06 16:11 ` Vipin Varghese
0 siblings, 0 replies; 2+ messages in thread
From: Vipin Varghese @ 2018-02-06 16:11 UTC (permalink / raw)
To: dev, pablo.de.lara.guarch
Cc: stable, john.mcnamara, marko.kovacevic, Vipin Varghese
Add infomration to explain applications using multiple instances of sw
crypto with example.
Signed-off-by: Vipin Varghese <vipin.varghese@intel.com>
---
V3 Changes:
- moved the multiple sw crypto to more generic place holder - Pablo
V2 Changes:
- Updated Note for better wording - Pablo
- Multiple instance information to Crypto Device Lib - Pablo
---
doc/guides/prog_guide/cryptodev_lib.rst | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/doc/guides/prog_guide/cryptodev_lib.rst b/doc/guides/prog_guide/cryptodev_lib.rst
index 2b338b9..d11e377 100644
--- a/doc/guides/prog_guide/cryptodev_lib.rst
+++ b/doc/guides/prog_guide/cryptodev_lib.rst
@@ -70,6 +70,15 @@ From the command line using the --vdev EAL option
--vdev 'crypto_aesni_mb0,max_nb_queue_pairs=2,max_nb_sessions=1024,socket_id=0'
+.. Note::
+
+ * If DPDK application requires multiple software crypto PMD devices then required
+ number of ``--vdev`` with appropriate libraries are to be added.
+
+ * An Application with crypto PMD instaces sharing the same library requires unique ID.
+
+ Example: ``--vdev 'crypto_aesni_mb0' --vdev 'crypto_aesni_mb1'``
+
Our using the rte_vdev_init API within the application code.
.. code-block:: c
--
1.9.1
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-02-06 16:11 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <1517841119-9277-1-git-send-email-vipin.varghese@intel.com>
2018-02-06 13:43 ` [dpdk-stable] [PATCH v2] doc: update multiple instance info for NULL crypto Vipin Varghese
2018-02-06 16:11 ` [dpdk-stable] [PATCH v3] doc: add info on multiple instance SW crypto Vipin Varghese
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).