From: <guyk@marvell.com>
To: <jerinj@marvell.com>, <ndabilpuram@marvell.com>,
<thomas@monjalon.net>, <mdr@ashroe.eu>, <nhorman@tuxdriver.com>,
<bruce.richardson@intel.com>, <anatoly.burakov@intel.com>,
<john.mcnamara@intel.com>, <marko.kovacevic@intel.com>
Cc: <dev@dpdk.org>, <smadarf@marvell.com>, <dovrat@marvell.com>,
<guyk@marvell.com>, <orika@mellanox.com>
Subject: [dpdk-dev] [PATCH 0/4] Add Marvell OCTEON TX2 regex driver
Date: Tue, 1 Sep 2020 15:24:32 +0300 [thread overview]
Message-ID: <20200901122436.17748-1-guyk@marvell.com> (raw)
From: Guy Kaneti <guyk@marvell.com>
This patchset adds support for OCTEON TX2 regex driver as DPDK regexdev.
The driver implements the API defined in the regexdev lib.
Guy Kaneti (4):
common/octeontx2: add REE definitions and logging support
regex/octeontx2: add build infra and device support
usertools: add octeontx2 REE device binding
doc: add Marvell OCTEON TX2 regex guide
MAINTAINERS | 3 +
config/common_base | 6 +
doc/guides/platform/octeontx2.rst | 5 +
doc/guides/regexdevs/features/octeontx2.ini | 10 +
doc/guides/regexdevs/index.rst | 1 +
doc/guides/regexdevs/octeontx2.rst | 49 +
doc/guides/rel_notes/release_20_11.rst | 5 +
drivers/common/octeontx2/hw/otx2_ree.h | 27 +
drivers/common/octeontx2/hw/otx2_rvu.h | 5 +
drivers/common/octeontx2/otx2_common.c | 1 +
drivers/common/octeontx2/otx2_common.h | 5 +
drivers/common/octeontx2/otx2_mbox.h | 103 ++
.../rte_common_octeontx2_version.map | 1 +
drivers/regex/meson.build | 2 +-
drivers/regex/octeontx2/meson.build | 53 +
drivers/regex/octeontx2/otx2_regexdev.c | 1001 +++++++++++++++++
drivers/regex/octeontx2/otx2_regexdev.h | 109 ++
.../regex/octeontx2/otx2_regexdev_compiler.c | 229 ++++
.../regex/octeontx2/otx2_regexdev_compiler.h | 11 +
.../regex/octeontx2/otx2_regexdev_hw_access.c | 167 +++
.../regex/octeontx2/otx2_regexdev_hw_access.h | 202 ++++
drivers/regex/octeontx2/otx2_regexdev_mbox.c | 401 +++++++
drivers/regex/octeontx2/otx2_regexdev_mbox.h | 38 +
.../rte_pmd_octeontx2_regex_version.map | 3 +
meson_options.txt | 2 +
usertools/dpdk-devbind.py | 8 +
26 files changed, 2446 insertions(+), 1 deletion(-)
create mode 100644 doc/guides/regexdevs/features/octeontx2.ini
create mode 100644 doc/guides/regexdevs/octeontx2.rst
create mode 100644 drivers/common/octeontx2/hw/otx2_ree.h
create mode 100644 drivers/regex/octeontx2/meson.build
create mode 100644 drivers/regex/octeontx2/otx2_regexdev.c
create mode 100644 drivers/regex/octeontx2/otx2_regexdev.h
create mode 100644 drivers/regex/octeontx2/otx2_regexdev_compiler.c
create mode 100644 drivers/regex/octeontx2/otx2_regexdev_compiler.h
create mode 100644 drivers/regex/octeontx2/otx2_regexdev_hw_access.c
create mode 100644 drivers/regex/octeontx2/otx2_regexdev_hw_access.h
create mode 100644 drivers/regex/octeontx2/otx2_regexdev_mbox.c
create mode 100644 drivers/regex/octeontx2/otx2_regexdev_mbox.h
create mode 100644 drivers/regex/octeontx2/rte_pmd_octeontx2_regex_version.map
--
2.28.0
next reply other threads:[~2020-09-01 12:26 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 12:24 guyk [this message]
2020-09-01 12:24 ` [dpdk-dev] [PATCH 1/4] common/octeontx2: add REE definitions and logging support guyk
2020-10-11 7:35 ` Liron Himi
2020-09-01 12:24 ` [dpdk-dev] [PATCH 2/4] regex/octeontx2: add build infra and device support guyk
2020-10-11 7:36 ` Liron Himi
2020-09-01 12:24 ` [dpdk-dev] [PATCH 3/4] usertools: add octeontx2 REE device binding guyk
2020-10-11 7:36 ` Liron Himi
2020-09-01 12:24 ` [dpdk-dev] [PATCH 4/4] doc: add Marvell OCTEON TX2 regex guide guyk
2020-10-11 7:36 ` Liron Himi
2020-10-08 6:31 ` [dpdk-dev] [PATCH 0/4] Add Marvell OCTEON TX2 regex driver Guy Kaneti
2020-10-11 21:23 ` Thomas Monjalon
2020-10-12 11:34 ` [dpdk-dev] [EXT] " Guy Kaneti
2020-10-12 11:31 ` [dpdk-dev] [PATCH v2 " guyk
2020-10-12 11:31 ` [dpdk-dev] [PATCH v2 1/4] common/octeontx2: add REE definitions and logging support guyk
2020-10-12 11:31 ` [dpdk-dev] [PATCH v2 2/4] regex/octeontx2: add build infra and device support guyk
2020-10-12 14:33 ` Thomas Monjalon
2020-10-12 17:06 ` [dpdk-dev] [EXT] " Guy Kaneti
2020-10-12 17:10 ` Thomas Monjalon
2020-10-12 17:13 ` Guy Kaneti
2020-10-12 17:19 ` Thomas Monjalon
2020-10-12 11:31 ` [dpdk-dev] [PATCH v2 3/4] usertools: add octeontx2 REE device binding guyk
2020-10-12 14:35 ` Thomas Monjalon
2020-10-12 11:31 ` [dpdk-dev] [PATCH v2 4/4] doc: add Marvell OCTEON TX2 regex guide guyk
2020-10-12 14:38 ` Thomas Monjalon
2020-10-12 17:09 ` [dpdk-dev] [EXT] " Guy Kaneti
2020-10-12 17:12 ` Thomas Monjalon
2020-10-13 10:10 ` [dpdk-dev] [PATCH v3 0/3] Add Marvell OCTEON TX2 regex driver guyk
2020-10-13 10:10 ` [dpdk-dev] [PATCH v3 1/3] common/octeontx2: add REE definitions and logging support guyk
2020-10-14 8:18 ` Thomas Monjalon
2020-10-13 10:10 ` [dpdk-dev] [PATCH v3 2/3] regex/octeontx2: add build infra and device support guyk
2020-10-14 8:26 ` Thomas Monjalon
2020-10-13 10:10 ` [dpdk-dev] [PATCH v3 3/3] usertools: add octeontx2 REE device binding guyk
2020-10-14 8:42 ` [dpdk-dev] [PATCH v3 0/3] Add Marvell OCTEON TX2 regex driver 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=20200901122436.17748-1-guyk@marvell.com \
--to=guyk@marvell.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dovrat@marvell.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=mdr@ashroe.eu \
--cc=ndabilpuram@marvell.com \
--cc=nhorman@tuxdriver.com \
--cc=orika@mellanox.com \
--cc=smadarf@marvell.com \
--cc=thomas@monjalon.net \
/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).