From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3 1/3] crypto/scheduler: add fail-over scheduling mode file
Date: Tue, 28 Mar 2017 23:09:30 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8974770E231@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1490711441-55895-2-git-send-email-roy.fan.zhang@intel.com>
Hi Fan,
> -----Original Message-----
> From: Zhang, Roy Fan
> Sent: Tuesday, March 28, 2017 3:31 PM
> To: dev@dpdk.org
> Cc: De Lara Guarch, Pablo; Gonzalez Monroy, Sergio; Doherty, Declan
> Subject: [PATCH v3 1/3] crypto/scheduler: add fail-over scheduling mode
> file
>
> This patch adds the fail-over scheduling mode main source file. Fail-over
> mode works with 2 slaves, primary slave and secondary slave. In this mode,
> the scheduler will enqueues the incoming crypto op burst to the primary
> slave. When one or more crypto ops are failed to be enqueued, they then
> will be enqueued to the secondary slave.
>
> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
Could you update release notes doc? Also for the packet size based scheduling mode.
Thanks,
Pablo
next prev parent reply other threads:[~2017-03-28 23:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 14:30 [dpdk-dev] [PATCH v3 0/3] crypto/scheduler: add fail-over mode 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 [this message]
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 ` [dpdk-dev] [PATCH v4 0/3] crypto/scheduler: add fail-over mode Fan Zhang
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=E115CCD9D858EF4F90C690B0DCB4D8974770E231@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=roy.fan.zhang@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).