From: Declan Doherty <declan.doherty@intel.com>
To: Fan Zhang <roy.fan.zhang@intel.com>, dev@dpdk.org
Cc: pablo.de.lara.guarch@intel.com, sergio.gonzalez.monroy@intel.com
Subject: Re: [dpdk-dev] [PATCH v4 1/3] crypto/scheduler: add packet size based mode code
Date: Thu, 30 Mar 2017 08:38:25 +0100 [thread overview]
Message-ID: <7348f306-324a-e825-b3a3-15ffb54b7287@intel.com> (raw)
In-Reply-To: <1490775959-65295-2-git-send-email-roy.fan.zhang@intel.com>
On 29/03/2017 9:25 AM, Fan Zhang wrote:
> This patch adds the packet size based distribution mode main source
> file.
>
> Packet-size based distribution mode is a scheduling mode works with 2
> slaves, the primary slave and the secondary slave, and distributes the
> enqueued crypto operations to them based on their data lengths. A crypto
> operation will be distributed to the primary slave if its data length is
> equal to or bigger than than the designated threshold, otherwise it will
> be handled by the secondary slave.
>
> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> ---
...
>
Acked-by: Declan Doherty <declan.doherty@intel.com>
next prev parent reply other threads:[~2017-03-30 7:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 14:09 [dpdk-dev] [PATCH v3 0/3] crypto/scheduler: add packet-base scheduling mode Fan Zhang
2017-03-28 14:09 ` [dpdk-dev] [PATCH v3 1/3] crypto/scheduler: add packet size based mode code Fan Zhang
2017-03-28 14:09 ` [dpdk-dev] [PATCH v3 2/3] crypto/scheduler: enable packet size based scheduling mode Fan Zhang
2017-03-28 14:09 ` [dpdk-dev] [PATCH v3 3/3] doc: update cryptodev scheduler PMD documentation Fan Zhang
2017-03-29 8:25 ` [dpdk-dev] [PATCH v4 0/3] crypto/scheduler: add packet-base scheduling mode Fan Zhang
2017-03-29 8:25 ` [dpdk-dev] [PATCH v4 1/3] crypto/scheduler: add packet size based mode code Fan Zhang
2017-03-30 7:38 ` Declan Doherty [this message]
2017-03-29 8:25 ` [dpdk-dev] [PATCH v4 2/3] crypto/scheduler: enable packet size based scheduling mode Fan Zhang
2017-03-29 8:25 ` [dpdk-dev] [PATCH v4 3/3] doc: update cryptodev scheduler PMD documentation Fan Zhang
2017-03-29 9:57 ` Mcnamara, John
2017-03-29 16:26 ` [dpdk-dev] [PATCH v5 0/3] crypto/scheduler: add packet-base scheduling mode Fan Zhang
2017-03-29 16:26 ` [dpdk-dev] [PATCH v5 1/3] crypto/scheduler: add packet size based mode code Fan Zhang
2017-03-29 20:09 ` De Lara Guarch, Pablo
2017-03-29 16:26 ` [dpdk-dev] [PATCH v5 2/3] crypto/scheduler: enable packet size based scheduling mode Fan Zhang
2017-03-29 16:26 ` [dpdk-dev] [PATCH v5 3/3] doc: update cryptodev scheduler PMD documentation Fan Zhang
2017-03-30 10:47 ` [dpdk-dev] [PATCH v6 0/3] crypto/scheduler: add packet-base scheduling mode Fan Zhang
2017-03-30 10:47 ` [dpdk-dev] [PATCH v6 1/3] crypto/scheduler: add packet size based mode code Fan Zhang
2017-03-30 11:16 ` Declan Doherty
2017-03-30 10:47 ` [dpdk-dev] [PATCH v6 2/3] crypto/scheduler: enable packet size based scheduling mode Fan Zhang
2017-03-30 11:17 ` Declan Doherty
2017-03-30 10:47 ` [dpdk-dev] [PATCH v6 3/3] doc: update cryptodev scheduler PMD documentation Fan Zhang
2017-03-30 11:17 ` Declan Doherty
2017-03-30 12:10 ` [dpdk-dev] [PATCH v6 0/3] crypto/scheduler: add packet-base scheduling 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=7348f306-324a-e825-b3a3-15ffb54b7287@intel.com \
--to=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--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).