DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pablo de Lara <pablo.de.lara.guarch@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/6] L2fwd-crypto enhancements
Date: Fri, 11 Mar 2016 00:02:45 +0000	[thread overview]
Message-ID: <1457654571-17432-1-git-send-email-pablo.de.lara.guarch@intel.com> (raw)

This patchset cleans up the l2fwd-crypto app,
implements some missing functionality
and makes use of the new capability discovery mechanism
that cryptodev library offers to discover which crypto operations
a PMD can provide.

This patchset depends on "cryptodev: add capabilities discovery mechanism" patch
(http://dpdk.org/dev/patchwork/patch/11434/)

Pablo de Lara (6):
  l2fwd-crypto: code cleanup
  l2fwd-crypto: update auth algo list
  l2fwd-crypto: implement parse_key function
  l2fwd_crypto: add AAD parsing
  l2fwd-crypto: add missing cipher/hash only cases
  l2fwd-crypto: use cryptodev capability discovery

 examples/l2fwd-crypto/main.c | 517 +++++++++++++++++++++++++++++--------------
 1 file changed, 348 insertions(+), 169 deletions(-)

-- 
2.5.0

             reply	other threads:[~2016-03-11  0:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11  0:02 Pablo de Lara [this message]
2016-03-11  0:02 ` [dpdk-dev] [PATCH 1/6] l2fwd-crypto: code cleanup Pablo de Lara
2016-03-11  0:02 ` [dpdk-dev] [PATCH 2/6] l2fwd-crypto: update auth algo list Pablo de Lara
2016-03-11  0:02 ` [dpdk-dev] [PATCH 3/6] l2fwd-crypto: implement parse_key function Pablo de Lara
2016-03-11  0:02 ` [dpdk-dev] [PATCH 4/6] l2fwd_crypto: add AAD parsing Pablo de Lara
2016-03-11  0:02 ` [dpdk-dev] [PATCH 5/6] l2fwd-crypto: add missing cipher/hash only cases Pablo de Lara
2016-03-11  0:02 ` [dpdk-dev] [PATCH 6/6] l2fwd-crypto: use cryptodev capability discovery Pablo de Lara
2016-03-11  6:57 ` [dpdk-dev] [PATCH 0/6] L2fwd-crypto enhancements Cao, Min
2016-03-11 10:02 ` Sergio Gonzalez Monroy
2016-03-11 10:50   ` 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=1457654571-17432-1-git-send-email-pablo.de.lara.guarch@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).