From: x-fn-spp-ml@ntt-tx.co.jp
To: spp@dpdk.org, ferruh.yigit@intel.com, yasufum.o@gmail.com
Subject: [spp] [PATCH v2 00/11] Add Hardware offload document
Date: Fri, 27 Mar 2020 13:57:21 +0900 [thread overview]
Message-ID: <20200327045732.18463-1-x-fn-spp-ml@ntt-tx.co.jp> (raw)
In-Reply-To: <20200226113521.3787-1-x-fn-spp-ml@ntt-tx.co.jp>
From: Hideyuki Yamashita <yamashita.hideyuki@ntt-tx.co.jp>
This patch set provides documents of hardware offload
capability for spp.
---
v2:
* resolve warning on both setup.rst and hardware-offload.rst.
Hideyuki Yamashita (11):
docs: add support for rte_flow
docs: add support of MLX5 PMD support in DPDK
docs: change primary process startup parameter
docs: add description of REST-APIs for flow rules
docs: support flow syntax in primary command
docs: support multi-queue in spp_vf command
docs: add svg for classify case of hardware offload
docs: add svg for vlan case of hardware offload
docs: add svg for vm case of hardware offload
docs: add usecase for hardware offload
docs: add install drivers for Mellanox NIC
docs/guides/api_ref/spp_primary.rst | 208 ++++
docs/guides/commands/primary.rst | 99 +-
docs/guides/commands/secondary/spp_vf.rst | 54 +-
docs/guides/design/spp_primary.rst | 3 +
docs/guides/gsg/howto_use.rst | 20 +
docs/guides/gsg/install.rst | 25 +-
docs/guides/gsg/setup.rst | 13 +
.../spp_hardware_offload_classify.svg | 680 +++++++++++
.../use_cases/spp_hardware_offload_vlan.svg | 805 +++++++++++++
.../use_cases/spp_hardware_offload_vm.svg | 1063 +++++++++++++++++
docs/guides/usecases/hardware-offload.rst | 328 +++++
docs/guides/usecases/index.rst | 1 +
12 files changed, 3256 insertions(+), 43 deletions(-)
create mode 100644 docs/guides/images/setup/use_cases/spp_hardware_offload_classify.svg
create mode 100644 docs/guides/images/setup/use_cases/spp_hardware_offload_vlan.svg
create mode 100644 docs/guides/images/setup/use_cases/spp_hardware_offload_vm.svg
create mode 100644 docs/guides/usecases/hardware-offload.rst
--
2.17.1
next parent reply other threads:[~2020-03-27 4:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200226113521.3787-1-x-fn-spp-ml@ntt-tx.co.jp>
2020-03-27 4:57 ` x-fn-spp-ml [this message]
2020-03-27 4:57 ` [spp] [PATCH v2 01/11] docs: add support for rte_flow x-fn-spp-ml
2020-03-27 4:57 ` [spp] [PATCH v2 02/11] docs: add support of MLX5 PMD support in DPDK x-fn-spp-ml
2020-03-27 4:57 ` [spp] [PATCH v2 03/11] docs: change primary process startup parameter x-fn-spp-ml
2020-03-27 4:57 ` [spp] [PATCH v2 04/11] docs: add description of REST-APIs for flow rules x-fn-spp-ml
2020-03-27 4:57 ` [spp] [PATCH v2 05/11] docs: support flow syntax in primary command x-fn-spp-ml
2020-03-27 4:57 ` [spp] [PATCH v2 06/11] docs: support multi-queue in spp_vf command x-fn-spp-ml
2020-03-27 4:57 ` [spp] [PATCH v2 07/11] docs: add svg for classify case of hardware offload x-fn-spp-ml
2020-03-27 4:57 ` [spp] [PATCH v2 08/11] docs: add svg for vlan " x-fn-spp-ml
2020-03-27 4:57 ` [spp] [PATCH v2 09/11] docs: add svg for vm " x-fn-spp-ml
2020-03-27 4:57 ` [spp] [PATCH v2 10/11] docs: add usecase for " x-fn-spp-ml
2020-03-27 4:57 ` [spp] [PATCH v2 11/11] docs: add install drivers for Mellanox NIC x-fn-spp-ml
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=20200327045732.18463-1-x-fn-spp-ml@ntt-tx.co.jp \
--to=x-fn-spp-ml@ntt-tx.co.jp \
--cc=ferruh.yigit@intel.com \
--cc=spp@dpdk.org \
--cc=yasufum.o@gmail.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).