DPDK patches and discussions
 help / color / mirror / Atom feed
From: Fan Zhang <roy.fan.zhang@intel.com>
To: dev@dpdk.org
Cc: pablo.de.lara.guarch@intel.com, sergio.gonzalez.monroy@intel.com,
	declan.doherty@intel.com
Subject: [dpdk-dev] [PATCH v2 3/3] doc: update cryptodev scheduler PMD documentation
Date: Thu, 23 Mar 2017 11:03:31 +0000	[thread overview]
Message-ID: <1490267011-57454-4-git-send-email-roy.fan.zhang@intel.com> (raw)
In-Reply-To: <1490267011-57454-1-git-send-email-roy.fan.zhang@intel.com>

This patch updates packet size based scheduling mode description.

Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
---
 doc/guides/cryptodevs/scheduler.rst | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/doc/guides/cryptodevs/scheduler.rst b/doc/guides/cryptodevs/scheduler.rst
index 70fb62e..51f2a78 100644
--- a/doc/guides/cryptodevs/scheduler.rst
+++ b/doc/guides/cryptodevs/scheduler.rst
@@ -126,3 +126,17 @@ operation:
    among its slaves in a round-robin manner. This mode may help to fill
    the throughput gap between the physical core and the existing cryptodevs
    to increase the overall performance.
+
+*   **CDEV_SCHED_MODE_PKT_SIZE_DISTR:**
+
+   Packet-size based distribution mode, which works with 2 slaves, primary
+   slave and secondary slave, and distribute the enqueued crypto ops to them
+   based on their data lengths. A crypto op will be distributed to the primary
+   slave if its data length equals or bigger than the designated threshold,
+   otherwise it will be handled by the secondary slave.
+
+   A typical usecase of this mode is with QAT cryptodev as primary and a
+   software cryptodev as secondary slave. This may help the application being
+   capable of processing extra crypto workload than what the sole QAT cryptodev
+   can handle, by making use of the available CPU cycles to deal with lesser
+   crypto workloads.
-- 
2.7.4

  parent reply	other threads:[~2017-03-23 11:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23 11:03 [dpdk-dev] [PATCH v2 0/3] crypto/scheduler: add packet-base scheduling mode Fan Zhang
2017-03-23 11:03 ` [dpdk-dev] [PATCH v2 1/3] crypto/scheduler: add packet size based mode code Fan Zhang
2017-03-28 10:37   ` Declan Doherty
2017-03-23 11:03 ` [dpdk-dev] [PATCH v2 2/3] crypto/scheduler: enable packet size based scheduling mode Fan Zhang
2017-03-23 11:03 ` Fan Zhang [this message]
2017-03-23 13:02 [dpdk-dev] [PATCH v2 0/3] crypto/scheduler: add fail-over mode Fan Zhang
2017-03-23 13:02 ` [dpdk-dev] [PATCH v2 3/3] doc: update cryptodev scheduler PMD documentation Fan Zhang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1490267011-57454-4-git-send-email-roy.fan.zhang@intel.com \
    --to=roy.fan.zhang@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=sergio.gonzalez.monroy@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).