DPDK patches and discussions
 help / color / mirror / Atom feed
From: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
To: dev@dpdk.org, Thomas Monjalon <thomasm@mellanox.com>
Subject: [dpdk-dev] [PATCH] ethdev: fix missing function in map file
Date: Fri, 13 Jul 2018 11:11:30 +0200	[thread overview]
Message-ID: <8e6234ad484ada96596a95eb302caeaed39b9c47.1531473066.git.nelio.laranjeiro@6wind.com> (raw)
In-Reply-To: <c24b09ef576d64846b39584ee7fd6a88cf93e80e.1531470241.git.nelio.laranjeiro@6wind.com>

Fixes: 4ed05fcd441b ("ethdev: add flow API to expand RSS flows")

Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>

--

Changes in v2:

- add missing documentation.
- add missing __rte_experimental in source file.
- update the order in map file.
---
 lib/librte_ethdev/rte_ethdev_version.map | 1 +
 lib/librte_ethdev/rte_flow.c             | 2 +-
 lib/librte_ethdev/rte_flow_driver.h      | 3 ++-
 3 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/lib/librte_ethdev/rte_ethdev_version.map b/lib/librte_ethdev/rte_ethdev_version.map
index 9a0d12d41..38f117f01 100644
--- a/lib/librte_ethdev/rte_ethdev_version.map
+++ b/lib/librte_ethdev/rte_ethdev_version.map
@@ -239,6 +239,7 @@ EXPERIMENTAL {
 	rte_eth_dev_tx_offload_name;
 	rte_eth_switch_domain_alloc;
 	rte_eth_switch_domain_free;
+	rte_flow_expand_rss;
 	rte_mtr_capabilities_get;
 	rte_mtr_create;
 	rte_mtr_destroy;
diff --git a/lib/librte_ethdev/rte_flow.c b/lib/librte_ethdev/rte_flow.c
index e06cc2193..cff4b5209 100644
--- a/lib/librte_ethdev/rte_flow.c
+++ b/lib/librte_ethdev/rte_flow.c
@@ -531,7 +531,7 @@ rte_flow_copy(struct rte_flow_desc *desc, size_t len,
  * Expand RSS flows into several possible flows according to the RSS hash
  * fields requested and the driver capabilities.
  */
-int
+int __rte_experimental
 rte_flow_expand_rss(struct rte_flow_expand_rss *buf, size_t size,
 		    const struct rte_flow_item *pattern, uint64_t types,
 		    const struct rte_flow_expand_node graph[],
diff --git a/lib/librte_ethdev/rte_flow_driver.h b/lib/librte_ethdev/rte_flow_driver.h
index ca675f6d3..4d8908226 100644
--- a/lib/librte_ethdev/rte_flow_driver.h
+++ b/lib/librte_ethdev/rte_flow_driver.h
@@ -148,6 +148,7 @@ struct rte_flow_expand_rss {
 /**
  * Expand RSS flows into several possible flows according to the RSS hash
  * fields requested and the driver capabilities.
+ * @b EXPERIMENTAL: this API may change without prior notice
  *
  * @param[out] buf
  *   Buffer to store the result expansion.
@@ -169,7 +170,7 @@ struct rte_flow_expand_rss {
  *
  *   -E2BIG: graph-depth @p graph is too deep.
  */
-int
+int __rte_experimental
 rte_flow_expand_rss(struct rte_flow_expand_rss *buf, size_t size,
 		    const struct rte_flow_item *pattern, uint64_t types,
 		    const struct rte_flow_expand_node graph[],
-- 
2.18.0

  parent reply	other threads:[~2018-07-13  9:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-13  8:24 Nelio Laranjeiro
2018-07-13  8:52 ` De Lara Guarch, Pablo
2018-07-13  9:09   ` Nélio Laranjeiro
2018-07-13  9:11 ` Nelio Laranjeiro [this message]
2018-07-13 13:54   ` 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=8e6234ad484ada96596a95eb302caeaed39b9c47.1531473066.git.nelio.laranjeiro@6wind.com \
    --to=nelio.laranjeiro@6wind.com \
    --cc=dev@dpdk.org \
    --cc=thomasm@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).