DPDK patches and discussions
 help / color / mirror / Atom feed
From: Martin Havlik <xhavli56@stud.fit.vutbr.cz>
To: xhavli56@stud.fit.vutbr.cz, Ori Kam <orika@nvidia.com>,
	Ajit Khaparde <ajit.khaparde@broadcom.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Andrew Rybchenko <arybchenko@solarflare.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	Dekel Peled <dekelp@nvidia.com>, Bing Zhao <bingz@nvidia.com>,
	Gregory Etelson <getelson@nvidia.com>,
	Eli Britstein <elibr@mellanox.com>,
	Alexander Kozyrev <akozyrev@nvidia.com>
Cc: dev@dpdk.org, Jan Viktorin <viktorin@cesnet.cz>
Subject: [dpdk-dev] [PATCH 2/4] doc: specify RTE flow create behaviour
Date: Wed, 21 Jul 2021 17:58:14 +0200
Message-ID: <20210721155816.188795-3-xhavli56@stud.fit.vutbr.cz> (raw)

The ability to create RTE flow rules, depending on
port status, can and does differ between PMDs.
Now the doc reflects that.

Signed-off-by: Martin Havlik <xhavli56@stud.fit.vutbr.cz>
 doc/guides/prog_guide/rte_flow.rst | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst
index 2b42d5ec8c..2988e3328a 100644
--- a/doc/guides/prog_guide/rte_flow.rst
+++ b/doc/guides/prog_guide/rte_flow.rst
@@ -3097,6 +3097,10 @@ actually created and a handle returned.
                    const struct rte_flow_action *actions[],
                    struct rte_flow_error *error);
+The ability to create a flow rule may depend on the status (started/stopped)
+of the port for which the rule is being created. This behaviour is
+PMD specific. Seek relevant PMD documentation for details.
 - ``port_id``: port identifier of Ethernet device.

             reply	other threads:[~2021-07-21 15:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21 15:58 Martin Havlik [this message]
2021-07-21 15:58 ` [dpdk-dev] [PATCH 3/4] doc: update bonding mode 8023ad info Martin Havlik
2021-07-26  1:39   ` Min Hu (Connor)
2021-07-21 18:16 ` [dpdk-dev] [PATCH 2/4] doc: specify RTE flow create behaviour Stephen Hemminger
2021-07-22 10:33   ` Andrew Rybchenko
2021-07-26  3:07   ` Ajit Khaparde
2021-07-26  6:46     ` Ori Kam
2021-07-26 14:52       ` Ajit Khaparde

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210721155816.188795-3-xhavli56@stud.fit.vutbr.cz \
    --to=xhavli56@stud.fit.vutbr.cz \
    --cc=ajit.khaparde@broadcom.com \
    --cc=akozyrev@nvidia.com \
    --cc=arybchenko@solarflare.com \
    --cc=bingz@nvidia.com \
    --cc=dekelp@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=elibr@mellanox.com \
    --cc=ferruh.yigit@intel.com \
    --cc=getelson@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=thomas@monjalon.net \
    --cc=viktorin@cesnet.cz \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git