From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v5] null_crypto_pmd: PMD to support null crypto operations
Date: Fri, 11 Mar 2016 02:15:31 +0100 [thread overview]
Message-ID: <4133523.tsRHzmSpqY@xps13> (raw)
In-Reply-To: <1457658250-156878-1-git-send-email-pablo.de.lara.guarch@intel.com>
2016-03-11 01:04, Pablo de Lara:
> 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>
Applied with a small doc indent fix, thanks
prev parent reply other threads:[~2016-03-11 1:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 20:48 [PATCH] null_crypto_pmd: PMD to support null crypto operations Declan Doherty
2016-03-10 16:46 ` [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 ` [PATCH v3] " Pablo de Lara
2016-03-11 0:45 ` De Lara Guarch, Pablo
2016-03-11 0:50 ` [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 ` [PATCH v5] " Pablo de Lara
2016-03-11 1:15 ` Thomas Monjalon [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=4133523.tsRHzmSpqY@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.