From: Declan Doherty <declan.doherty@intel.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: dev@dpdk.org, Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com>
Subject: Re: [dpdk-dev] [PATCH v4] cryptodev: remove crypto device type enumeration
Date: Mon, 3 Jul 2017 10:47:42 +0100 [thread overview]
Message-ID: <b4b22c4e-8f92-6d41-4e41-f5d705838087@intel.com> (raw)
In-Reply-To: <20170630143421.24250-1-pablo.de.lara.guarch@intel.com>
On 30/06/2017 3:34 PM, Pablo de Lara wrote:
> From: Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com>
>
> Changes device type identification to be based on a unique
> driver id replacing the current device type enumeration, which needed
> library changes every time a new crypto driver was added.
>
> The driver id is assigned dynamically during driver registration using
> the new macro RTE_PMD_REGISTER_CRYPTO_DRIVER which returns a unique
> uint8_t identifier for that driver. New APIs are also introduced
> to allow retrieval of the driver id using the driver name.
>
> Signed-off-by: Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com>
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> ---
...
>
Acked-by: Declan Doherty <declan.doherty@intel.com>
next prev parent reply other threads:[~2017-07-03 9:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 9:55 [dpdk-dev] [PATCH] " Slawomir Mrozowicz
2017-05-17 9:00 ` De Lara Guarch, Pablo
2017-05-22 11:10 ` [dpdk-dev] [PATCH v2] " Slawomir Mrozowicz
2017-06-30 14:10 ` [dpdk-dev] [PATCH v3] " Pablo de Lara
2017-06-30 14:34 ` [dpdk-dev] [PATCH v4] " Pablo de Lara
2017-07-03 9:47 ` Declan Doherty [this message]
2017-07-04 10:16 ` 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=b4b22c4e-8f92-6d41-4e41-f5d705838087@intel.com \
--to=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=slawomirx.mrozowicz@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).