From: Thomas Monjalon <thomas@monjalon.net>
To: Bing Zhao <bingz@mellanox.com>
Cc: john.mcnamara@intel.com, marko.kovacevic@intel.com,
viacheslavo@mellanox.com, orika@mellanox.com, matan@mellanox.com,
shahafs@mellanox.com, rasland@mellanox.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3] doc: update flow non-cached mode notes
Date: Wed, 22 Apr 2020 04:09:19 +0200 [thread overview]
Message-ID: <5073065.29KlJPOoH8@thomas> (raw)
In-Reply-To: <1587449290-124383-1-git-send-email-bingz@mellanox.com>
Hi,
Please prefer splitting lines after punctuation signs.
21/04/2020 08:08, Bing Zhao:
> --- a/doc/guides/nics/mlx5.rst
> +++ b/doc/guides/nics/mlx5.rst
>
> +Notes for rte_flow
A blank line is missing below:
> +------------------
> +Implementation of flows organization is in non-cached mode. When stopping a
This can be simpler in direct form:
Flows are not cached in the driver.
> +device, all the flows inserted from application will be considered invalid and
device -> device port
> +flushed automatically in the background. After restarting of the device, no
restarting of the device -> restarting the device
> +application's flow exists in the system. All reference pointers to these flows
Why "application's flow"?
What about "no flow is represented in the system"?
reference pointers -> references
> +held by the application are not valid anymore and should be discarded by the
> +application.
Invalid and discard explanations are repeated below.
> +
> +The application should recreate the flows as required after device restarting,
device restarting -> port restart
Better to stop the sentence here, and move it at the end of the paragraph after "stop".
> +and must not try to destroy or flush the invalid flows after stopping (except
After stopping, flows become invalid.
They should be discarded but neither destroyed nor flushed.
> +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.
Removed flow rules caching for memory saving and compliance with ethdev API.
next prev parent reply other threads:[~2020-04-22 2:09 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 [this message]
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=5073065.29KlJPOoH8@thomas \
--to=thomas@monjalon.net \
--cc=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=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).