From: Sean Zhang <xiazhang@nvidia.com>
Cc: <dev@dpdk.org>
Subject: [v1 0/4] Add support for modifying ECN in IPv4/IPv6 header
Date: Sat, 2 Apr 2022 10:11:46 +0300 [thread overview]
Message-ID: <20220402071150.9392-1-xiazhang@nvidia.com> (raw)
This patch set adds support for modifying ECN fields in IPv4/IPv6
header, and also adds support for modify_filed action in meter.
Jiawei Wang (1):
ethdev: add IPv4/IPv6 ECN header rewrite action
Sean Zhang (3):
common/mlx5: add modify ECN capability check
net/mlx5: add support to modify ECN field
net/mlx5: add modify field support in meter
app/test-pmd/cmdline_flow.c | 3 +-
doc/guides/nics/mlx5.rst | 4 +-
drivers/common/mlx5/mlx5_devx_cmds.c | 3 ++
drivers/common/mlx5/mlx5_devx_cmds.h | 1 +
drivers/common/mlx5/mlx5_prm.h | 62 ++++++++++++++++++++++++-
drivers/net/mlx5/mlx5_flow.c | 5 +-
drivers/net/mlx5/mlx5_flow.h | 2 +
drivers/net/mlx5/mlx5_flow_dv.c | 69 ++++++++++++++++++++++++++--
drivers/net/mlx5/mlx5_flow_meter.c | 2 +-
lib/ethdev/rte_flow.h | 2 +
10 files changed, 143 insertions(+), 10 deletions(-)
--
2.31.1
next reply other threads:[~2022-04-02 7:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 7:11 Sean Zhang [this message]
2022-04-02 7:11 ` [v1 1/4] ethdev: add IPv4/IPv6 ECN header rewrite action Sean Zhang
2022-06-01 18:51 ` Ferruh Yigit
2022-06-02 5:48 ` Ori Kam
2022-06-02 11:44 ` Ferruh Yigit
2022-04-02 7:11 ` [v1 2/4] common/mlx5: add modify ECN capability check Sean Zhang
2022-06-06 8:05 ` Slava Ovsiienko
2022-04-02 7:11 ` [v1 3/4] net/mlx5: add support to modify ECN field Sean Zhang
2022-06-06 7:17 ` Slava Ovsiienko
2022-04-02 7:11 ` [v1 4/4] net/mlx5: add modify field support in meter Sean Zhang
2022-06-06 7:18 ` Slava Ovsiienko
2022-06-01 18:51 ` [v1 0/4] Add support for modifying ECN in IPv4/IPv6 header Ferruh Yigit
2022-06-02 11:44 ` Ferruh Yigit
2022-06-02 13:13 ` Sean Zhang (Networking SW)
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=20220402071150.9392-1-xiazhang@nvidia.com \
--to=xiazhang@nvidia.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).