From: Raslan Darawsheh <rasland@mellanox.com>
To: thomas@monjalon.net
Cc: dev@dpdk.org, orika@mellanox.com
Subject: [dpdk-dev] [PATCH] doc: update mlx5 encap/decap limitations
Date: Sun, 23 Feb 2020 11:30:59 +0200 [thread overview]
Message-ID: <1582450259-7235-1-git-send-email-rasland@mellanox.com> (raw)
Document validation limitations for encap/decap.
Signed-off-by: Raslan Darawsheh <rasland@mellanox.com>
Acked-by: Ori kam <orika@mellanox.com>
---
doc/guides/nics/mlx5.rst | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index dd2fbde..7991da9 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -215,6 +215,17 @@ Limitations
- Rx queue with LRO offload enabled, receiving a non-LRO packet, can forward
it with size limited to max LRO size, not to max RX packet length.
+- Decap / raw_decap:
+
+ - The decap is always done up to the first HW detected tunnel.
+ - Decap buffer is not validated, only matters for deciding the decap type
+ l3/l2 decap using the buffer size.
+
+- Encap / raw_encap:
+
+ - No validation is done on the encap buffer, it's user responsibility to
+ provide valid buffer.
+
Statistics
----------
--
2.7.4
next reply other threads:[~2020-02-23 9:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-23 9:30 Raslan Darawsheh [this message]
2020-02-25 12:32 ` 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=1582450259-7235-1-git-send-email-rasland@mellanox.com \
--to=rasland@mellanox.com \
--cc=dev@dpdk.org \
--cc=orika@mellanox.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).