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] crypto/scheduler: change enqueue and dequeue functions
Date: Mon, 20 Mar 2017 14:18:25 +0000 [thread overview]
Message-ID: <1820d55e-0583-905f-cc4b-8df4d7d47d26@intel.com> (raw)
In-Reply-To: <1488453131-94845-1-git-send-email-roy.fan.zhang@intel.com>
On 02/03/17 11:12, Fan Zhang wrote:
> This patch changes the enqueue and dequeue methods to cryptodev
> scheduler PMD. Originally a 2-layer function call is carried out
> upon enqueuing or dequeuing a burst of crypto ops. This patch
> removes one layer to improve the performance.
>
> 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-20 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 11:12 Fan Zhang
2017-03-20 14:18 ` Declan Doherty [this message]
2017-03-21 17:17 ` 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=1820d55e-0583-905f-cc4b-8df4d7d47d26@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).