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
Subject: Re: [dpdk-dev] [PATCH 2/3] crypto/scheduler: improve slave configuration
Date: Thu, 23 Mar 2017 15:09:36 +0000 [thread overview]
Message-ID: <97e16f3e-0a4d-aed3-1663-600dbca36f98@intel.com> (raw)
In-Reply-To: <1487332862-5719-3-git-send-email-roy.fan.zhang@intel.com>
On 17/02/17 12:01, Fan Zhang wrote:
> Since the new device configuration API is updated, we can make use of
> this feature to the crypto scheduler PMD to configure its slaves
> automatically with the same configurations it got. As originally the
> slaves have to be manually configured one by one, this patch should
> help reducing the coding complexity.
>
> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> ---
...
>
This patch needs to rebased due to the movement of app/test/ to test/test
next prev parent reply other threads:[~2017-03-23 15:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 12:00 [dpdk-dev] [PATCH 0/3] cryptodev: change device configuration API Fan Zhang
2017-02-17 12:01 ` [dpdk-dev] [PATCH 1/3] " Fan Zhang
2017-03-23 14:55 ` Declan Doherty
2017-02-17 12:01 ` [dpdk-dev] [PATCH 2/3] crypto/scheduler: improve slave configuration Fan Zhang
2017-03-23 14:58 ` Declan Doherty
2017-03-23 15:09 ` Declan Doherty [this message]
2017-03-23 15:13 ` De Lara Guarch, Pablo
2017-02-17 12:01 ` [dpdk-dev] [PATCH 3/3] doc: remove deprecation notice Fan Zhang
2017-02-20 15:20 ` Mcnamara, John
2017-03-27 13:23 ` [dpdk-dev] [PATCH 0/3] cryptodev: change device configuration API 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=97e16f3e-0a4d-aed3-1663-600dbca36f98@intel.com \
--to=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=roy.fan.zhang@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).