From: Declan Doherty <declan.doherty@intel.com>
To: dev@dpdk.org
Cc: Declan Doherty <declan.doherty@intel.com>
Subject: [dpdk-dev] [PATCH 0/2] cryptodev documentation patches
Date: Fri, 8 Apr 2016 17:17:25 +0100 [thread overview]
Message-ID: <1460132247-16553-1-git-send-email-declan.doherty@intel.com> (raw)
Add an overview section to the cryptodev guide which outlines each PMD supported
algorithms.
Add new chapter to the DPDK user guide for the cryptodev library
Declan Doherty (2):
docs: add cryptodevs guide overview section
docs: cryptodev chapter for programmer's guide
doc/guides/cryptodevs/index.rst | 3 +-
doc/guides/cryptodevs/overview.rst | 94 ++++
doc/guides/prog_guide/cryptodev_lib.rst | 584 +++++++++++++++++++++++
doc/guides/prog_guide/img/crypto_op.svg | 75 +++
doc/guides/prog_guide/img/crypto_xform_chain.svg | 145 ++++++
doc/guides/prog_guide/img/cryptodev_sym_sess.svg | 66 +++
doc/guides/prog_guide/index.rst | 1 +
7 files changed, 967 insertions(+), 1 deletion(-)
create mode 100644 doc/guides/cryptodevs/overview.rst
create mode 100644 doc/guides/prog_guide/cryptodev_lib.rst
create mode 100644 doc/guides/prog_guide/img/crypto_op.svg
create mode 100644 doc/guides/prog_guide/img/crypto_xform_chain.svg
create mode 100644 doc/guides/prog_guide/img/cryptodev_sym_sess.svg
--
2.5.5
next reply other threads:[~2016-04-08 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 16:17 Declan Doherty [this message]
2016-04-08 16:17 ` [dpdk-dev] [PATCH 1/2] docs: add cryptodevs guide overview section Declan Doherty
2016-04-08 18:13 ` De Lara Guarch, Pablo
2016-04-08 20:08 ` Mcnamara, John
2016-04-08 16:17 ` [dpdk-dev] [PATCH 2/2] docs: cryptodev chapter for programmer's guide Declan Doherty
2016-04-08 18:16 ` De Lara Guarch, Pablo
2016-04-08 20:05 ` Mcnamara, John
2016-04-08 22:41 ` 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=1460132247-16553-1-git-send-email-declan.doherty@intel.com \
--to=declan.doherty@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).