From: Bing Zhao <bingz@mellanox.com>
To: john.mcnamara@intel.com, marko.kovacevic@intel.com,
viacheslavo@mellanox.com, orika@mellanox.com, matan@mellanox.com
Cc: shahafs@mellanox.com, rasland@mellanox.com, dev@dpdk.org,
thomas@monjalon.net
Subject: [dpdk-dev] [PATCH v3] doc: update flow non-cached mode notes
Date: Tue, 21 Apr 2020 14:08:10 +0800 [thread overview]
Message-ID: <1587449290-124383-1-git-send-email-bingz@mellanox.com> (raw)
In-Reply-To: <1586789756-227464-1-git-send-email-bingz@mellanox.com>
This patch updates the MLX5 PMD and release notes documentations.
Adding the notes of the behavior change that rte flows organization
is switched into non-cached mode for applications.
Signed-off-by: Bing Zhao <bingz@mellanox.com>
---
v2: update the description in release notes.
v3: update the notes of rte_flow for application.
---
doc/guides/nics/mlx5.rst | 13 +++++++++++++
doc/guides/rel_notes/release_20_05.rst | 2 ++
2 files changed, 15 insertions(+)
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index 759d0ac..ced5e03 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -1300,6 +1300,19 @@ set, and we should allow to specify zero values as rte_flow parameters for the
META and MARK items and actions. In the same time zero mask has no meaning and
should be rejected on validation stage.
+Notes for rte_flow
+------------------
+Implementation of flows organization is in non-cached mode. When stopping a
+device, all the flows inserted from application will be considered invalid and
+flushed automatically in the background. After restarting of the device, no
+application's flow exists in the system. All reference pointers to these flows
+held by the application are not valid anymore and should be discarded by the
+application.
+
+The application should recreate the flows as required after device restarting,
+and must not try to destroy or flush the invalid flows after stopping (except
+discarding them).
+
Notes for testpmd
-----------------
diff --git a/doc/guides/rel_notes/release_20_05.rst b/doc/guides/rel_notes/release_20_05.rst
index bacd4c6..367c5df 100644
--- a/doc/guides/rel_notes/release_20_05.rst
+++ b/doc/guides/rel_notes/release_20_05.rst
@@ -63,6 +63,8 @@ New Features
* Added support for matching on IPv4 Time To Live and IPv6 Hop Limit.
* Added support for creating Relaxed Ordering Memory Regions.
* Added support for jumbo frame size (9K MTU) in Multi-Packet RQ mode.
+ * Flow rules caching removed from the driver for memory saving and
+ correctness according to RTE flow and RTE ethdev.
* Optimized the memory consumption of flow.
* **Updated the Intel ice driver.**
--
1.8.3.1
next prev parent reply other threads:[~2020-04-21 6:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 14:55 [dpdk-dev] [PATCH v2] " Bing Zhao
2020-04-20 10:09 ` Ori Kam
2020-04-21 6:08 ` Bing Zhao [this message]
2020-04-21 6:39 ` [dpdk-dev] [PATCH v3] " Ori Kam
2020-04-22 2:09 ` Thomas Monjalon
2020-04-22 9:23 ` [dpdk-dev] [PATCH v4] " Bing Zhao
2020-04-22 11:07 ` Thomas Monjalon
2020-04-22 15:27 ` [dpdk-dev] [PATCH v5] " Bing Zhao
2020-05-05 9:39 ` Raslan Darawsheh
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=1587449290-124383-1-git-send-email-bingz@mellanox.com \
--to=bingz@mellanox.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=matan@mellanox.com \
--cc=orika@mellanox.com \
--cc=rasland@mellanox.com \
--cc=shahafs@mellanox.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@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).