From: Gregory Etelson <getelson@nvidia.com>
To: <dev@dpdk.org>, <getelson@nvidia.com>
Cc: <viacheslavo@nvidia.com>, <matan@nvidia.com>,
<rasland@nvidia.com>, <thomas@monjalon.net>
Subject: [PATCH] doc: add mlx5 PMD flex item documentation
Date: Tue, 16 Nov 2021 16:51:39 +0200 [thread overview]
Message-ID: <20211116145139.837-1-getelson@nvidia.com> (raw)
Describe firmware configuration requirements.
List mlx5 hardware and PMD limitations.
Signed-off-by: Gregory Etelson <getelson@nvidia.com>
---
doc/guides/nics/mlx5.rst | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index 552e06c0db..bbeeb1a3d4 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -494,6 +494,17 @@ Limitations
from the reference "Clock Queue" completions,
the scheduled send timestamps should not be specified with non-zero MSB.
+- Flex item API:
+
+ - Firmware configuration: ``FLEX_PARSER_PROFILE_ENABLE=4 PROG_PARSE_GRAPH=1``.
+ - Hardware support: BlueField-2.
+ - Flex item is supported on PF only.
+ - Hardware limits ``header_length_mask_width`` up to 6 bits.
+ - Firmware supports 8 global sample fields. Each flex item allocates non-shared sample fields from that pool.
+ - Supported flex item can have 1 IN arc - ``eth`` or ``udp`` and up to 2 OUT arcs - ``ipv4`` or ``ipv6``.
+ - Flex item fields (next_header, next_protocol, samples) do not participate in RSS hash functions.
+ - In RTE flex item configuration, ``next_header.field_base`` value must be byte aligned (multiple of 8).
+
Statistics
----------
@@ -1260,6 +1271,11 @@ Below are some firmware configurations listed.
REAL_TIME_CLOCK_ENABLE=1
+- enable dynamic flex parser for RTE flex item::
+
+ FLEX_PARSER_PROFILE_ENABLE=4
+ PROG_PARSE_GRAPH=1
+
Linux Prerequisites
-------------------
--
2.33.1
next reply other threads:[~2021-11-16 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 14:51 Gregory Etelson [this message]
2021-11-16 15:05 ` Thomas Monjalon
2021-11-16 15:45 ` [PATCH v2] " Gregory Etelson
2021-11-22 10:42 ` Slava Ovsiienko
2021-11-23 9:29 ` [PATCH v3] " Gregory Etelson
2021-11-23 17:35 ` 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=20211116145139.837-1-getelson@nvidia.com \
--to=getelson@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=rasland@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@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).