From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] null_crypto_pmd: PMD to support null crypto operations
Date: Fri, 11 Mar 2016 00:45:50 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C8C8605@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1457656984-154437-1-git-send-email-pablo.de.lara.guarch@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Pablo de Lara
> Sent: Friday, March 11, 2016 12:43 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH v3] null_crypto_pmd: PMD to support null crypto
> operations
>
> From: Declan Doherty <declan.doherty@intel.com>
>
> This patch provides the implementation of a NULL crypto PMD, which
> supports
> NULL cipher and NULL authentication operations, which can be chained
> together
> as follows:
>
> - Authentication Only
> - Cipher Only
> - Authentication then Cipher
> - Cipher then Authentication
>
> As this is a NULL operation device the crypto operations which are submitted
> for
> processing are not actually modified and are stored in a queue pairs
> processed
> packets ring ready for collection when rte_cryptodev_burst_dequeue() is
> called.
>
> The patch also contains the related unit tests function to test the PMDs
> supported operations.
>
> Signed-off-by: Declan Doherty <declan.doherty@intel.com>
> Acked-by: Deepak Kumar JAIN<deepak.k.jain@intel.com>
> ---
>
> This patch depends on "AES GCM, AES CMAC fixes and addition of GCM
> tests for QAT" patchset
> (http://dpdk.org/ml/archives/dev/2016-March/034974.html)
>
> Changes in v2:
> - Rebased to include Cryptodev API changes
>
> Changes in v3:
>
> - Added missing doc reference in MAINTAINERS
> - Removed attempt to remove a reference already delated
>
>
> MAINTAINERS | 4 +
> app/test/test_cryptodev.c | 402
> ++++++++++++++++++++++++++++++++-
> config/common_base | 5 +
> doc/guides/cryptodevs/index.rst | 3 +-
> doc/guides/rel_notes/release_16_04.rst | 3 +
> drivers/crypto/Makefile | 1 +
> mk/rte.app.mk | 1 +
> 7 files changed, 417 insertions(+), 2 deletions(-)
Self-NACK again, actual driver was not included...
next prev parent reply other threads:[~2016-03-11 0:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 20:48 [dpdk-dev] [PATCH] " Declan Doherty
2016-03-10 16:46 ` [dpdk-dev] [PATCH v2] " Pablo de Lara
2016-03-10 16:49 ` Jain, Deepak K
2016-03-11 0:39 ` De Lara Guarch, Pablo
2016-03-11 0:43 ` [dpdk-dev] [PATCH v3] " Pablo de Lara
2016-03-11 0:45 ` De Lara Guarch, Pablo [this message]
2016-03-11 0:50 ` [dpdk-dev] [PATCH v4] " Pablo de Lara
2016-03-11 0:56 ` Thomas Monjalon
2016-03-11 1:05 ` De Lara Guarch, Pablo
2016-03-11 1:04 ` [dpdk-dev] [PATCH v5] " Pablo de Lara
2016-03-11 1:15 ` Thomas Monjalon
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=E115CCD9D858EF4F90C690B0DCB4D8973C8C8605@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
/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).