From: Jiawei Wang <jiaweiw@nvidia.com>
To: <rasland@nvidia.com>, <thomas@monjalon.net>, <asafp@nvidia.com>,
"Matan Azrad" <matan@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
"Ori Kam" <orika@nvidia.com>, Sean Zhang <xiazhang@nvidia.com>
Cc: <dev@dpdk.org>
Subject: [PATCH] doc: add IP ECN header rewrite to mlx5 notes
Date: Mon, 11 Jul 2022 12:58:58 +0300 [thread overview]
Message-ID: <20220711095858.48269-1-jiaweiw@nvidia.com> (raw)
This patch updates the mlx5 notes for IPv4/IPv6 ECN field
rewrite offload.
Fixes: c4e442fa4c45 ("ethdev: add IPv4/IPv6 ECN header rewrite action")
Fixes: 097d84a42a87 ("common/mlx5: check ECN modification capability")
Fixes: 76d575612277 ("net/mlx5: support modifying ECN field")
Signed-off-by: Jiawei Wang <jiaweiw@nvidia.com>
Acked-by: Asaf Penso <asafp@nvidia.com>
---
doc/guides/nics/mlx5.rst | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index a7f9851d16..eb16669b3f 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -1355,6 +1355,11 @@ Supported hardware offloads
| | | | rdma-core 24 | | rdma-core 24 |
| | | | ConnectX-5 | | ConnectX-5 |
+-----------------------+-----------------+-----------------+
+ | | Header rewrite | | DPDK 22.07 | | DPDK 22.07 |
+ | | (ipv4_ecn) | | OFED 5.6-2 | | OFED 5.6-2 |
+ | | ipv6_ecn) | | rdma-core 41 | | rdma-core 41 |
+ | | | | ConnectX-5 | | ConnectX-5 |
+ +-----------------------+-----------------+-----------------+
| Jump | | DPDK 19.05 | | DPDK 19.02 |
| | | OFED 4.7-1 | | OFED 4.7-1 |
| | | rdma-core 24 | | N/A |
--
2.18.1
next reply other threads:[~2022-07-11 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 9:58 Jiawei Wang [this message]
2022-07-11 10:49 ` David Marchand
2022-07-11 17:56 ` 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=20220711095858.48269-1-jiaweiw@nvidia.com \
--to=jiaweiw@nvidia.com \
--cc=asafp@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.com \
--cc=xiazhang@nvidia.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).