From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
dev@dpdk.org, "Doherty, Declan" <declan.doherty@intel.com>,
Shahaf Shuler <shahafs@mellanox.com>,
"John Daley (johndale)" <johndale@cisco.com>,
Nelio Laranjeiro <nelio.laranjeiro@6wind.com>,
"Xueming(Steven) Li" <xuemingl@mellanox.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] [PATCH v1 2/4] doc: announce API change for flow RSS action
Date: Wed, 14 Feb 2018 16:37:31 +0100 [thread overview]
Message-ID: <20180214152847.19774-3-adrien.mazarguil@6wind.com> (raw)
In-Reply-To: <20180214152847.19774-1-adrien.mazarguil@6wind.com>
Since its inception, the rte_flow RSS action has been relying in part on
struct rte_eth_rss_conf for compatibility with the legacy RSS API. This
structure lacks parameters such as the hash function to use, and more
recently, a method to tell which layer RSS should be performed on [1].
Given struct rte_eth_rss_conf will never be flexible enough to represent a
complete RSS configuration (e.g. RETA table), struct rte_flow_action_rss
will be extended instead.
Depending on the outcome of RSS level implementation work, this deprecation
notice may either cancel or come in conjunction with [1].
[1] http://dpdk.org/ml/archives/dev/2018-February/090359.html
Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
---
doc/guides/rel_notes/deprecation.rst | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 663550acb..40b76b391 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -67,3 +67,8 @@ Deprecation Notices
(non-)terminating property of actions will be discarded. Instead, flow
rules themselves will be considered terminating by default unless a
PASSTHRU action is also specified.
+
+* rte_flow: RSS action will stop relying on the legacy ``struct
+ rte_eth_rss_conf`` due to its limitations. All parameters, including the
+ currently missing hash function to use will be made part of ``struct
+ rte_flow_action_rss`` directly.
--
2.11.0
next prev parent reply other threads:[~2018-02-14 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 15:37 [dpdk-dev] [PATCH v1 0/4] doc: announce API changes for flow rules Adrien Mazarguil
2018-02-14 15:37 ` [dpdk-dev] [PATCH v1 1/4] doc: announce API change for flow actions Adrien Mazarguil
2018-02-14 15:37 ` Adrien Mazarguil [this message]
2018-02-14 15:37 ` [dpdk-dev] [PATCH v1 3/4] doc: announce API change for flow RSS/RAW actions Adrien Mazarguil
2018-02-14 15:37 ` [dpdk-dev] [PATCH v1 4/4] doc: announce API change for flow VLAN pattern item Adrien Mazarguil
2018-02-14 15:55 ` [dpdk-dev] [PATCH v1 0/4] doc: announce API changes for flow rules Nélio Laranjeiro
2018-02-14 16:06 ` Andrew Rybchenko
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=20180214152847.19774-3-adrien.mazarguil@6wind.com \
--to=adrien.mazarguil@6wind.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=johndale@cisco.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=nhorman@tuxdriver.com \
--cc=shahafs@mellanox.com \
--cc=thomas@monjalon.net \
--cc=xuemingl@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).