From: Thomas Monjalon <thomas@monjalon.net>
To: john.mcnamara@intel.com, marko.kovacevic@intel.com,
viacheslavo@mellanox.com, matan@mellanox.com,
Bing Zhao <bingz@mellanox.com>
Cc: shahafs@mellanox.com, rasland@mellanox.com, orika@mellanox.com,
dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: update flow non-cached mode notes
Date: Fri, 10 Apr 2020 12:09:30 +0200 [thread overview]
Message-ID: <3767470.ZaRXLXkqSa@thomas> (raw)
In-Reply-To: <1586511374-331792-1-git-send-email-bingz@mellanox.com>
10/04/2020 11:36, Bing Zhao:
> 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.
Please, can it be squashed in the patch doing this change?
> + * Flows organization changed from cached mode to non-cached mode.
I suggest this wording:
Flow rules caching removed from the driver for memory saving.
next prev parent reply other threads:[~2020-04-10 10:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 9:36 Bing Zhao
2020-04-10 10:09 ` Thomas Monjalon [this message]
2020-04-10 10:18 ` Bing Zhao
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=3767470.ZaRXLXkqSa@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).