From: Xiaoyu Min <jackmin@mellanox.com>
To: viacheslavo@mellanox.com, matan@mellanox.com, rasland@mellanox.com
Cc: dev@dpdk.org
Subject: [dpdk-dev] [RFC 0/4] net/mlx5: dump software steering flows in HW
Date: Tue, 14 Jan 2020 05:45:11 +0200 [thread overview]
Message-ID: <cover.1578969179.git.jackmin@mellanox.com> (raw)
This RFC intends to provide a way to dump all the offloaded rte flows
in HW. This is very helpful for user and developer to debug flow offloading
stuff, i.e, to check whether PMD offloads the rte flow in a correct way
from HW perspective.
A private PMD API is provided as well as a socket server for external tool
to trigger dump.
The output file is in raw format and Mellanox specific. An external vendor
(Mellanox) provided tool is needed in order to get human readable format.
Please be aware the underlying rdma-core lib also needs to support this.
Xueming Li (4):
net/mlx5: support flow dump Api
app/testpmd: new flow dump CLI
net/mlx5: add socket server for external tools
doc: update mlx5 document for flow dump feature
app/test-pmd/Makefile | 4 +
app/test-pmd/cmdline_flow.c | 91 +++++++++
app/test-pmd/config.c | 33 ++++
app/test-pmd/meson.build | 3 +
app/test-pmd/testpmd.h | 1 +
doc/guides/nics/mlx5.rst | 28 +++
drivers/net/mlx5/Makefile | 12 +-
drivers/net/mlx5/meson.build | 5 +
drivers/net/mlx5/mlx5.c | 2 +
drivers/net/mlx5/mlx5.h | 7 +
drivers/net/mlx5/mlx5_devx_cmds.c | 35 ++++
drivers/net/mlx5/mlx5_glue.c | 13 ++
drivers/net/mlx5/mlx5_glue.h | 1 +
drivers/net/mlx5/mlx5_socket.c | 226 ++++++++++++++++++++++
drivers/net/mlx5/rte_pmd_mlx5.c | 22 +++
drivers/net/mlx5/rte_pmd_mlx5.h | 39 ++++
drivers/net/mlx5/rte_pmd_mlx5_version.map | 7 +
17 files changed, 528 insertions(+), 1 deletion(-)
create mode 100644 drivers/net/mlx5/mlx5_socket.c
create mode 100644 drivers/net/mlx5/rte_pmd_mlx5.c
create mode 100644 drivers/net/mlx5/rte_pmd_mlx5.h
--
2.24.1
next reply other threads:[~2020-01-14 3:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 3:45 Xiaoyu Min [this message]
2020-01-14 3:45 ` [dpdk-dev] [RFC 1/4] net/mlx5: support flow dump Api Xiaoyu Min
2020-01-14 3:45 ` [dpdk-dev] [RFC 2/4] app/testpmd: new flow dump CLI Xiaoyu Min
2020-01-14 4:31 ` Jerin Jacob
2020-01-14 10:15 ` Jack Min
2020-01-14 14:00 ` Jerin Jacob
2020-01-15 12:49 ` Jack Min
2020-01-14 3:45 ` [dpdk-dev] [RFC 3/4] net/mlx5: add socket server for external tools Xiaoyu Min
2020-01-14 3:45 ` [dpdk-dev] [RFC 4/4] doc: update mlx5 document for flow dump feature Xiaoyu Min
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=cover.1578969179.git.jackmin@mellanox.com \
--to=jackmin@mellanox.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=rasland@mellanox.com \
--cc=viacheslavo@mellanox.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).