From: Dekel Peled <dekelp@mellanox.com>
To: wenzhuo.lu@intel.com, jingjing.wu@intel.com,
bernard.iremonger@intel.com, olivier.matz@6wind.com,
adrien.mazarguil@6wind.com, thomas@monjalon.net,
ferruh.yigit@intel.com, arybchenko@solarflare.com
Cc: shahafs@mellanox.com, dev@dpdk.org, orika@mellanox.com,
dekelp@mellanox.com
Subject: [dpdk-dev] [PATCH 2/2] ethdev: fix metadata documentation
Date: Tue, 23 Oct 2018 16:28:51 +0300 [thread overview]
Message-ID: <1540301331-51065-2-git-send-email-dekelp@mellanox.com> (raw)
In-Reply-To: <1540301331-51065-1-git-send-email-dekelp@mellanox.com>
Previous patch introduced the Tx metadata feature, with unnecessary
restrictions on data entry.
This fix updates the documentation, removing the data entry
restrictions on metadata item.
Fixes: aa0b9484eb5f ("ethdev: support metadata as flow rule criteria")
Cc: dekelp@mellanox.com
Signed-off-by: Dekel Peled <dekelp@mellanox.com>
---
doc/guides/prog_guide/rte_flow.rst | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst
index 6fb0535..d6683e4 100644
--- a/doc/guides/prog_guide/rte_flow.rst
+++ b/doc/guides/prog_guide/rte_flow.rst
@@ -1196,21 +1196,21 @@ Item: ``META``
Matches an application specific 32 bit metadata item.
-- Default ``mask`` matches the specified metadata value.
+- Default ``mask`` matches any 32 bit value.
.. _table_rte_flow_item_meta:
.. table:: META
- +----------+----------+-----------------------+
- | Field | Subfield | Value |
- +==========+==========+=======================+
- | ``spec`` | ``data`` | 32 bit metadata value |
- +----------+----------------------------------+
- | ``last`` | ``data`` | ignored |
- +----------+----------+-----------------------+
- | ``mask`` | ``data`` | ignored |
- +----------+----------+-----------------------+
+ +----------+----------+---------------------------------------+
+ | Field | Subfield | Value |
+ +==========+==========+=======================================+
+ | ``spec`` | ``data`` | 32 bit metadata value |
+ +----------+--------------------------------------------------+
+ | ``last`` | ``data`` | upper range value |
+ +----------+----------+---------------------------------------+
+ | ``mask`` | ``data`` | bit-mask applies to "spec" and "last" |
+ +----------+----------+---------------------------------------+
Actions
~~~~~~~
--
1.8.3.1
next prev parent reply other threads:[~2018-10-23 13:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 13:28 [dpdk-dev] [PATCH 1/2] app/testpmd: fix metadata API and Tx insertion Dekel Peled
2018-10-23 13:28 ` Dekel Peled [this message]
2018-10-23 18:05 ` [dpdk-dev] [PATCH 2/2] ethdev: fix metadata documentation Ori Kam
2018-10-24 5:54 ` Dekel Peled
2018-10-24 6:21 ` [dpdk-dev] [PATCH v2 1/2] app/testpmd: fix metadata API and Tx insertion Dekel Peled
2018-10-24 10:49 ` Ori Kam
2018-10-25 10:45 ` Ferruh Yigit
2018-10-25 11:32 ` Thomas Monjalon
2018-10-24 6:22 ` [dpdk-dev] [PATCH v2 2/2] ethdev: fix metadata documentation Dekel Peled
2018-10-24 10:43 ` Ori Kam
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=1540301331-51065-2-git-send-email-dekelp@mellanox.com \
--to=dekelp@mellanox.com \
--cc=adrien.mazarguil@6wind.com \
--cc=arybchenko@solarflare.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jingjing.wu@intel.com \
--cc=olivier.matz@6wind.com \
--cc=orika@mellanox.com \
--cc=shahafs@mellanox.com \
--cc=thomas@monjalon.net \
--cc=wenzhuo.lu@intel.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).