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 v2] crypto/scheduler: add mode specific option support
Date: Wed, 5 Apr 2017 08:46:58 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D89747802C57@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1490974226-40957-1-git-send-email-roy.fan.zhang@intel.com>
Hi Fan,
> -----Original Message-----
> From: Zhang, Roy Fan
> Sent: Friday, March 31, 2017 4:30 PM
> To: dev@dpdk.org
> Cc: De Lara Guarch, Pablo; Gonzalez Monroy, Sergio; Doherty, Declan
> Subject: [PATCH v2] crypto/scheduler: add mode specific option support
>
> Some scheduling modes may need extra options to be configured,
> this patch adds the function prototype for setting/getting
> options.
>
> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> ---
>
> v2:
> - Updated for option support in packet-size based mode
> - Updated version map file
>
> drivers/crypto/scheduler/rte_cryptodev_scheduler.c | 63
> ++++++++++++++++++++++
> drivers/crypto/scheduler/rte_cryptodev_scheduler.h | 55
> +++++++++++++++++++
> .../scheduler/rte_cryptodev_scheduler_operations.h | 13 +++++
> .../scheduler/rte_pmd_crypto_scheduler_version.map | 2 +
> drivers/crypto/scheduler/scheduler_failover.c | 2 +
> .../crypto/scheduler/scheduler_pkt_size_distr.c | 47 ++++++++++++++++
> drivers/crypto/scheduler/scheduler_roundrobin.c | 4 +-
> 7 files changed, 185 insertions(+), 1 deletion(-)
>
...
> diff --git
> a/drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
> b/drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
> index 69cf0c6..7c45eaf 100644
> --- a/drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
> +++ b/drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
> @@ -15,5 +15,7 @@ DPDK_17.05 {
> global:
>
> rte_cryptodev_scheduler_slaves_get;
> + rte_cryptodev_scheduler_option_set;
> + rte_cryptodev_scheduler_option_get;
This has to be in alphabetical order.
next prev parent reply other threads:[~2017-04-05 8:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 14:29 [dpdk-dev] [PATCH] " Fan Zhang
2017-03-21 14:34 ` De Lara Guarch, Pablo
2017-03-31 15:30 ` [dpdk-dev] [PATCH v2] " Fan Zhang
2017-04-05 8:46 ` De Lara Guarch, Pablo [this message]
2017-04-05 9:02 ` [dpdk-dev] [PATCH v3] " Fan Zhang
2017-04-05 10:02 ` Declan Doherty
2017-04-05 11:43 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2017-04-05 15:54 ` [dpdk-dev] [PATCH v4] " Fan Zhang
2017-04-05 16:07 ` [dpdk-dev] [PATCH v5] " Fan Zhang
2017-04-17 19:46 ` 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=E115CCD9D858EF4F90C690B0DCB4D89747802C57@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).