From: Suanming Mou <suanmingm@mellanox.com>
Cc: dev@dpdk.org, rasland@mellanox.com
Subject: [dpdk-dev] [PATCH v2 0/2] add IPv4/IPv6 DSCP rewrite action
Date: Tue, 7 Jan 2020 09:24:00 +0200 [thread overview]
Message-ID: <1578381843-110954-1-git-send-email-suanmingm@mellanox.com> (raw)
In-Reply-To: <1577945052-39548-1-git-send-email-suanmingm@mellanox.com>
For some overlay network, such as VXLAN, the DSCP field in the new outer
IP header after VXLAN decapsulation may need to be updated accordingly.
This patchset implements the DSCP rewrite action for IPv4 and IPv6 as RFC[1].
[1] https://inbox.dpdk.org/dev/1575955386-6672-1-git-send-email-suanmingm@mellanox.com/
---
v2: change the magic number 0x3f to RTE_IPV4/6_HDR_DSCP_MASK macro in PMD.
Suanming Mou (2):
ethdev: add IPv4/IPv6 DSCP rewrite action
net/mlx5: add IPv4/IPv6 DSCP rewrite action
app/test-pmd/cmdline_flow.c | 50 ++++++++
doc/guides/prog_guide/rte_flow.rst | 40 ++++++
doc/guides/testpmd_app_ug/testpmd_funcs.rst | 8 ++
drivers/net/mlx5/mlx5_flow.h | 6 +-
drivers/net/mlx5/mlx5_flow_dv.c | 184 ++++++++++++++++++++++++++++
lib/librte_ethdev/rte_flow.c | 2 +
lib/librte_ethdev/rte_flow.h | 31 +++++
7 files changed, 320 insertions(+), 1 deletion(-)
--
1.8.3.1
next prev parent reply other threads:[~2020-01-07 7:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 6:04 [dpdk-dev] [PATCH " Suanming Mou
2020-01-02 6:04 ` [dpdk-dev] [PATCH 1/2] ethdev: " Suanming Mou
2020-01-02 6:04 ` [dpdk-dev] [PATCH 2/2] net/mlx5: " Suanming Mou
2020-01-06 14:36 ` Matan Azrad
2020-01-07 6:33 ` Suanming Mou
2020-01-07 7:24 ` Suanming Mou [this message]
2020-01-07 7:24 ` [dpdk-dev] [PATCH v2 1/2] ethdev: " Suanming Mou
2020-01-07 7:24 ` [dpdk-dev] [PATCH v2 2/2] net/mlx5: " Suanming Mou
2020-01-07 7:26 ` Matan Azrad
2020-01-10 18:55 ` [dpdk-dev] [PATCH v2 0/2] " Ferruh Yigit
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=1578381843-110954-1-git-send-email-suanmingm@mellanox.com \
--to=suanmingm@mellanox.com \
--cc=dev@dpdk.org \
--cc=rasland@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).