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>
Subject: Re: [dpdk-dev] [PATCH] crypto/scheduler: add mode specific option support
Date: Tue, 21 Mar 2017 14:34:01 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D897476F2F61@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1487687379-43345-1-git-send-email-roy.fan.zhang@intel.com>
Hi Fan,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Fan Zhang
> Sent: Tuesday, February 21, 2017 2:30 PM
> To: dev@dpdk.org
> Cc: De Lara Guarch, Pablo
> Subject: [dpdk-dev] [PATCH] 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>
> ---
> drivers/crypto/scheduler/rte_cryptodev_scheduler.c | 57
> ++++++++++++++++++++++
> drivers/crypto/scheduler/rte_cryptodev_scheduler.h | 27 ++++++++++
> .../scheduler/rte_cryptodev_scheduler_operations.h | 5 ++
> drivers/crypto/scheduler/scheduler_roundrobin.c | 10 +++-
> 4 files changed, 98 insertions(+), 1 deletion(-)
>
You are adding two new functions to the API, so you should add them in the version.map file.
Thanks,
Pablo
next prev parent reply other threads:[~2017-03-21 14:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 14:29 Fan Zhang
2017-03-21 14:34 ` De Lara Guarch, Pablo [this message]
2017-03-31 15:30 ` [dpdk-dev] [PATCH v2] " Fan Zhang
2017-04-05 8:46 ` De Lara Guarch, Pablo
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=E115CCD9D858EF4F90C690B0DCB4D897476F2F61@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--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).