DPDK patches and discussions
 help / color / mirror / Atom feed
From: Declan Doherty <declan.doherty@intel.com>
To: Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [RFC] cryptodev: remove crypto device type enumeration
Date: Mon, 8 May 2017 11:35:30 +0100	[thread overview]
Message-ID: <6ff2bb9c-b1ba-0513-160f-60ab329fe2a0@intel.com> (raw)
In-Reply-To: <5b8225a8-e749-5f89-c6d6-d12cf7328057@intel.com>

On 05/05/2017 4:37 PM, Declan Doherty wrote:
> On 05/05/2017 12:07 PM, Slawomir Mrozowicz wrote:
>> This RFC 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.
>>
>> Library code is included in the RFC
>> (implementation in progress, API complete).
>>
>> Signed-off-by: Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com>
>> ---
> ....
>>
> Acked-by: Declan Doherty <declan.doherty@intel.com>

sorry please ignore this ack, it was meant for the doc announce patch 
regarding the same.

      reply	other threads:[~2017-05-08 10:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05 11:07 Slawomir Mrozowicz
2017-05-05 15:37 ` Declan Doherty
2017-05-08 10:35   ` Declan Doherty [this message]

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=6ff2bb9c-b1ba-0513-160f-60ab329fe2a0@intel.com \
    --to=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --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).