DPDK patches and discussions
 help / color / mirror / Atom feed
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 v5] doc: update flow non-cached mode notes
Date: Wed, 22 Apr 2020 23:27:15 +0800	[thread overview]
Message-ID: <1587569235-444742-1-git-send-email-bingz@mellanox.com> (raw)
In-Reply-To: <1587547392-380151-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>
Acked-by: Ori Kam <orika@mellanox.com>
---
v2: update the description in release notes.
v3: update the notes of rte_flow for application.
v4: update the descriptions.
v5: update the format of lines splitting.
---
 doc/guides/nics/mlx5.rst               | 14 ++++++++++++++
 doc/guides/rel_notes/release_20_05.rst |  1 +
 2 files changed, 15 insertions(+)

diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index 759d0ac..fd5b697 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -1290,6 +1290,7 @@ Supported hardware offloads
 
 Notes for metadata
 ------------------
+
 MARK and META items are interrelated with datapath - they might move from/to
 the applications in mbuf fields. Hence, zero value for these items has the
 special meaning - it means "no metadata are provided", not zero values are
@@ -1300,6 +1301,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
+------------------
+
+Flows are not cached in the driver.
+When stopping a device port, all the flows created on this port from the
+application will be flushed automatically in the background.
+After stopping the device port, all flows on this port become invalid and
+not represented in the system.
+All references to these flows held by the application should be discarded
+directly but neither destroyed nor flushed.
+
+The application should re-create the flows as required after the port restart.
+
 Notes for testpmd
 -----------------
 
diff --git a/doc/guides/rel_notes/release_20_05.rst b/doc/guides/rel_notes/release_20_05.rst
index 8c71dc1..e91fe14 100644
--- a/doc/guides/rel_notes/release_20_05.rst
+++ b/doc/guides/rel_notes/release_20_05.rst
@@ -79,6 +79,7 @@ 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.
+  * Removed flow rules caching for memory saving and compliance with ethdev API.
   * Optimized the memory consumption of flow.
 
 * **Updated the Intel ice driver.**
-- 
1.8.3.1


  parent reply	other threads:[~2020-04-22 15:27 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 ` [dpdk-dev] [PATCH v3] " Bing Zhao
2020-04-21  6:39   ` 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     ` Bing Zhao [this message]
2020-05-05  9:39       ` [dpdk-dev] [PATCH v5] " 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=1587569235-444742-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).