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 v4 0/3] crypto/scheduler: add fail-over mode
Date: Wed, 29 Mar 2017 09:24:25 +0100 [thread overview]
Message-ID: <1490775868-65199-1-git-send-email-roy.fan.zhang@intel.com> (raw)
In-Reply-To: <1490711441-55895-1-git-send-email-roy.fan.zhang@intel.com>
This patch adds fail-over mode for cryptodev scheduler PMD. Fail-over mode
works with 2 slaves, the primary slave and the secondary slave. In this
mode, the scheduler will enqueues the incoming crypto operation burst to the
primary slave. When one or more crypto operations fail to be enqueued, then
they will be enqueued to the secondary slave.
v4:
- Polished documentation.
- Fixed documentation grammer errors.
v3:
- More detailed commit messages.
- Removed device flush.
- Updated dequeue_ordering function
v2:
- Update with new reorder method
Fan Zhang (3):
crypto/scheduler: add fail-over scheduling mode file
crypto/scheduler: enable fail-over scheduling mode
doc: update cryptodev scheduler PMD documentation
doc/guides/cryptodevs/scheduler.rst | 8 +
drivers/crypto/scheduler/Makefile | 1 +
drivers/crypto/scheduler/rte_cryptodev_scheduler.c | 7 +
drivers/crypto/scheduler/rte_cryptodev_scheduler.h | 3 +
drivers/crypto/scheduler/scheduler_failover.c | 285 +++++++++++++++++++++
5 files changed, 304 insertions(+)
create mode 100644 drivers/crypto/scheduler/scheduler_failover.c
--
2.7.4
next prev parent reply other threads:[~2017-03-29 8:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 14:30 [dpdk-dev] [PATCH v3 " Fan Zhang
2017-03-28 14:30 ` [dpdk-dev] [PATCH v3 1/3] crypto/scheduler: add fail-over scheduling mode file Fan Zhang
2017-03-28 23:09 ` De Lara Guarch, Pablo
2017-03-28 14:30 ` [dpdk-dev] [PATCH v3 2/3] crypto/scheduler: enable fail-over scheduling mode Fan Zhang
2017-03-28 14:30 ` [dpdk-dev] [PATCH v3 3/3] doc: update cryptodev scheduler PMD documentation Fan Zhang
2017-03-29 8:24 ` Fan Zhang [this message]
2017-03-29 8:24 ` [dpdk-dev] [PATCH v4 1/3] crypto/scheduler: add fail-over scheduling mode file Fan Zhang
2017-03-29 8:24 ` [dpdk-dev] [PATCH v4 2/3] crypto/scheduler: enable fail-over scheduling mode Fan Zhang
2017-03-29 8:24 ` [dpdk-dev] [PATCH v4 3/3] doc: update cryptodev scheduler PMD documentation Fan Zhang
2017-03-29 9:52 ` Mcnamara, John
2017-03-29 11:29 ` [dpdk-dev] [PATCH v4 0/3] crypto/scheduler: add fail-over mode De Lara Guarch, Pablo
2017-03-29 12:46 ` Bruce Richardson
2017-03-29 16:31 ` [dpdk-dev] [PATCH v5 " Fan Zhang
2017-03-29 16:31 ` [dpdk-dev] [PATCH v5 1/3] crypto/scheduler: add fail-over scheduling mode file Fan Zhang
2017-03-30 7:43 ` Declan Doherty
2017-03-29 16:31 ` [dpdk-dev] [PATCH v5 2/3] crypto/scheduler: enable fail-over scheduling mode Fan Zhang
2017-03-30 7:48 ` Declan Doherty
2017-03-29 16:31 ` [dpdk-dev] [PATCH v5 3/3] doc: update cryptodev scheduler PMD documentation Fan Zhang
2017-03-30 7:48 ` Declan Doherty
2017-03-30 12:33 ` [dpdk-dev] [PATCH v5 0/3] crypto/scheduler: add fail-over mode De Lara Guarch, Pablo
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=1490775868-65199-1-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).