From: Michael Baum <michaelba@nvidia.com>
To: <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>,
Thomas Monjalon <thomas@monjalon.net>,
Raslan Darawsheh <rasland@nvidia.com>,
Aman Singh <aman.deep.singh@intel.com>,
Yuying Zhang <yuying.zhang@intel.com>,
"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>,
<michaelba@nvidia.com>
Subject: [PATCH v2 6/6] doc: add ethdev pre-config flags to release notes
Date: Wed, 16 Nov 2022 14:56:28 +0200 [thread overview]
Message-ID: <20221116125628.1026877-7-michaelba@nvidia.com> (raw)
In-Reply-To: <20221116125628.1026877-1-michaelba@nvidia.com>
Add to release notes:
1. Flags field in pre-configuration structure and strict-queue flag.
Fixes: dcc9a80c20b8 ("ethdev: add strict queue to pre-configuration flow hints")
Cc: michaelba@nvidia.com
Signed-off-by: Michael Baum <michaelba@nvidia.com>
Reviewed-by: Thomas Monjalon <thomas@monjalon.net>
---
doc/guides/rel_notes/release_22_11.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/doc/guides/rel_notes/release_22_11.rst b/doc/guides/rel_notes/release_22_11.rst
index ba8b97c09a..3dee012636 100644
--- a/doc/guides/rel_notes/release_22_11.rst
+++ b/doc/guides/rel_notes/release_22_11.rst
@@ -108,6 +108,12 @@ New Features
Each flag has a corresponding capability flag
in ``struct rte_eth_hairpin_queue_cap``.
+* **Added strict queue to pre-configuration flow hints.**
+
+ * Added flags option to ``rte_flow_configure`` and ``rte_flow_info_get``.
+ * Added ``RTE_FLOW_PORT_FLAG_STRICT_QUEUE`` flag to indicate all operations
+ for a given flow rule will strictly happen on the same queue.
+
* **Added configuration for asynchronous flow connection tracking.**
Added connection tracking action number hint to ``rte_flow_configure``
--
2.25.1
next prev parent reply other threads:[~2022-11-16 12:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 14:15 [PATCH 0/6] doc: some fixes Michael Baum
2022-11-10 14:15 ` [PATCH 1/6] doc: fix underlines too long in testpmd documentation Michael Baum
2022-11-11 7:07 ` Zhang, Yuying
2022-11-10 14:15 ` [PATCH 2/6] doc: fix the colon type in listing aged flow rules Michael Baum
2022-11-10 14:15 ` [PATCH 3/6] doc: fix miss blank line in testpmd flow syntax doc Michael Baum
2022-11-11 7:02 ` Zhang, Yuying
2022-11-10 14:15 ` [PATCH 4/6] doc: fix miss blank line in release notes Michael Baum
2022-11-10 14:15 ` [PATCH 5/6] doc: add mlx5 HWS aging support to " Michael Baum
2022-11-10 14:15 ` [PATCH 6/6] doc: add ethdev pre-config flags " Michael Baum
2022-11-16 12:56 ` [PATCH v2 0/6] doc: some fixes Michael Baum
2022-11-16 12:56 ` [PATCH v2 1/6] doc: fix underlines too long in testpmd documentation Michael Baum
2022-11-16 12:56 ` [PATCH v2 2/6] doc: fix the colon type in listing aged flow rules Michael Baum
2022-11-16 12:56 ` [PATCH v2 3/6] doc: fix miss blank line in testpmd flow syntax doc Michael Baum
2022-11-16 12:56 ` [PATCH v2 4/6] doc: fix miss blank line in release notes Michael Baum
2022-11-16 12:56 ` [PATCH v2 5/6] doc: add mlx5 HWS aging support to " Michael Baum
2022-11-16 12:56 ` Michael Baum [this message]
2022-11-21 21:29 ` [PATCH v2 0/6] doc: some fixes Thomas Monjalon
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=20221116125628.1026877-7-michaelba@nvidia.com \
--to=michaelba@nvidia.com \
--cc=aman.deep.singh@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=rasland@nvidia.com \
--cc=thomas@monjalon.net \
--cc=yuying.zhang@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).