Skip to contentSkip to conversation

ethdev: document special cases of port start and stop

PATCH Superseded Dariusz Sosnowski 4 participants 21 messages Nov 9, 2022 – Nov 21, 2022 Network drivers

lore
Share & tools
lore
#0 lore raw

cover ethdev: document special cases of port start and stop

This patch series attempts to address the special failure cases of rte_eth_dev_stop() and rte_eth_dev_start().

In case of starting a port, If the port depends on another one being started, PMDs might return (-EAGAIN) to notify about such situation.

In case of stopping a port, If the port cannot be stopped, because other port depends on its resources,
PMDs might return (-EBUSY) to notify about such situation.

These cases are addressed in ethdev API docs.
Testpmd is updated to allow users to manually retry start/stop operations.

Dariusz Sosnowski (3):
net/mlx5: fix log level on failed transfer proxy stop
doc: document E-Switch limitations with HWS in mlx5 PMD
ethdev: document special cases of port start and stop

 app/test-pmd/testpmd.c          | 10 +++++++++-
 doc/guides/nics/mlx5.rst        | 13 +++++++++++++
 drivers/net/mlx5/mlx5_trigger.c |  6 +++---
 lib/ethdev/rte_ethdev.h         |  9 +++++++++
 4 files changed, 34 insertions(+), 4 deletions(-)
Signature · 1 line
2.25.1
#1 lore raw

PATCH 1/3 net/mlx5: fix log level on failed transfer proxy stop

This patches increases log level for error reporting when stopping the transfer proxy port failed. Stopping can fail with EBUSY when related representor ports are still running.

Fixes 483181f7b6dd ("net/mlx5: support device control of representor matching")
---
 drivers/net/mlx5/mlx5_trigger.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/net/mlx5/mlx5_trigger.c +3 -3
index 4b821a1076..310a84729e 100644
@@ -1361,9 +1361,9 @@ mlx5_hw_proxy_port_allowed_stop(struct rte_eth_dev *dev)
 			representor_started = true;
 	}
 	if (representor_started) {
-		DRV_LOG(INFO, "Failed to stop port %u: attached representor ports"
-			      " must be stopped before stopping transfer proxy port",
-			      dev->data->port_id);
+		DRV_LOG(ERR, "Failed to stop port %u: attached representor ports"
+			     " must be stopped before stopping transfer proxy port",
+			     dev->data->port_id);
 		rte_errno = EBUSY;
 		return -rte_errno;
 	}
Signature · 1 line
2.25.1
#2 lore raw

PATCH 2/3 doc: document E-Switch limitations with HWS in mlx5 PMD

In reply to Dariusz Sosnowski

This patch adds the following limitations to the mlx5 PMD guide:

- With HW Steering and E-Switch enabled, transfer proxy port must be started before any port representor.
- With HW Steering and E-Switch enabled, all representors must be stopped before transfer proxy port is stopped.

---
 doc/guides/nics/mlx5.rst | 13 +++++++++++++
 1 file changed, 13 insertions(+)
doc/guides/nics/mlx5.rst +13 -0
index 4f0db21dde..7e39bb2ea5 100644
@@ -161,6 +161,19 @@ Limitations
   - NIC ConnectX-5 and before are not supported.
   - Partial match with item template is not supported.
   - IPv6 5-tuple matching is not supported.
+  - With E-Switch enabled, ports which share the E-Switch domain
+    should be started and stopped in a specific order:
+
+    - When starting ports, the transfer proxy port should be started first
+      and port representors should follow.
+    - When stopping ports, all of the port representors
+      should be stopped before stopping the transfer proxy port.
+
+    If ports are started/stopped in an incorrect order,
+    ``rte_eth_dev_start()``/``rte_eth_dev_stop()`` will return an appropriate error code:
+
+    - ``-EAGAIN`` for ``rte_eth_dev_start()``.
+    - ``-EBUSY`` for ``rte_eth_dev_stop().
 
 - When using Verbs flow engine (``dv_flow_en`` = 0), flow pattern without any
   specific VLAN will match for VLAN packets as well:
Signature · 1 line
2.25.1
#3 lore raw

PATCH 3/3 ethdev: document special cases of port start and stop

In reply to Dariusz Sosnowski

This patch clarifies the handling of following cases in the ethdev API docs:

- If rte_eth_dev_start() returns (-EAGAIN) for some port, it cannot be started until other port is started.
- If rte_eth_dev_stop() returns (-EBUSY) for some port, it cannot be stopped until other port is stopped.

When stopping the port in testpmd fails due to (-EBUSY), port's state is switched back to STARTED
to allow users to manually retry stopping the port.

No additional changes in testpmd are required to handle failure to start port with (-EAGAIN).
If rte_eth_dev_start() fails, port's state is switched to STOPPED and users are allowed to retry the operation.

---
 app/test-pmd/testpmd.c  | 10 +++++++++-
 lib/ethdev/rte_ethdev.h |  9 +++++++++
 2 files changed, 18 insertions(+), 1 deletion(-)
app/test-pmd/testpmd.c +9 -1
index 7381dfd9e5..c9252031e8 100644
@@ -3158,6 +3158,7 @@ stop_port(portid_t pid)
 	int need_check_link_status = 0;
 	portid_t peer_pl[RTE_MAX_ETHPORTS];
 	int peer_pi;
+	int ret;
 
 	if (port_id_is_invalid(pid, ENABLED_WARN))
 		return;
@@ -3207,9 +3208,16 @@ stop_port(portid_t pid)
 		if (port->flow_list)
 			port_flow_flush(pi);
 
-		if (eth_dev_stop_mp(pi) != 0)
+		ret = eth_dev_stop_mp(pi);
+		if (ret != 0) {
 			RTE_LOG(ERR, EAL, "rte_eth_dev_stop failed for port %u\n",
 				pi);
+			if (ret == -EBUSY) {
+				/* Allow to retry stopping the port. */
+				port->port_status = RTE_PORT_STARTED;
+				continue;
+			}
+		}
 
 		if (port->port_status == RTE_PORT_HANDLING)
 			port->port_status = RTE_PORT_STOPPED;
lib/ethdev/rte_ethdev.h +9 -0
index 13fe73d5a3..abf5a24f92 100644
@@ -2701,10 +2701,14 @@ int rte_eth_dev_tx_queue_stop(uint16_t port_id, uint16_t tx_queue_id);
  * On success, all basic functions exported by the Ethernet API (link status,
  * receive/transmit, and so on) can be invoked.
  *
+ * If the port depends on another one being started,
+ * PMDs might return (-EAGAIN) to notify about such requirement.
+ *
  * @param port_id
  *   The port identifier of the Ethernet device.
  * @return
  *   - 0: Success, Ethernet device started.
+ *   - -EAGAIN: If it depends on another port to be started first.
  *   - <0: Error code of the driver device start function.
  */
 int rte_eth_dev_start(uint16_t port_id);
@@ -2713,10 +2717,15 @@ int rte_eth_dev_start(uint16_t port_id);
  * Stop an Ethernet device. The device can be restarted with a call to
  * rte_eth_dev_start()
  *
+ * If the port provides some resources for other ports
+ * and it cannot be stopped before them,
+ * PMDs might return (-EBUSY) to notify about such requirement.
+ *
  * @param port_id
  *   The port identifier of the Ethernet device.
  * @return
  *   - 0: Success, Ethernet device stopped.
+ *   - -EBUSY: If it depends on another port to be stopped first.
  *   - <0: Error code of the driver device stop function.
  */
 int rte_eth_dev_stop(uint16_t port_id);
Signature · 1 line
2.25.1
#4 lore raw

v2 cover ethdev: document special cases of port start and stop

In reply to Dariusz Sosnowski

This patch series attempts to address the special failure cases of rte_eth_dev_stop() and rte_eth_dev_start().

In case of starting a port, If the port depends on another one being started, PMDs might return (-EAGAIN) to notify about such situation.

In case of stopping a port, If the port cannot be stopped, because other port depends on its resources,
PMDs might return (-EBUSY) to notify about such situation.

These cases are addressed in ethdev API docs.
Testpmd is updated to allow users to manually retry start/stop operations.

v2:
- Fixed documentation build.

Dariusz Sosnowski (3):
net/mlx5: fix log level on failed transfer proxy stop
doc: document E-Switch limitations with HWS in mlx5 PMD
ethdev: document special cases of port start and stop

 app/test-pmd/testpmd.c          | 10 +++++++++-
 doc/guides/nics/mlx5.rst        | 13 +++++++++++++
 drivers/net/mlx5/mlx5_trigger.c |  6 +++---
 lib/ethdev/rte_ethdev.h         |  9 +++++++++
 4 files changed, 34 insertions(+), 4 deletions(-)
Signature · 1 line
2.25.1
#5 lore raw

PATCH v2 1/3 net/mlx5: fix log level on failed transfer proxy stop

This patches increases log level for error reporting when stopping the transfer proxy port failed. Stopping can fail with EBUSY when related representor ports are still running.

Fixes 483181f7b6dd ("net/mlx5: support device control of representor matching")
---
 drivers/net/mlx5/mlx5_trigger.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/net/mlx5/mlx5_trigger.c +3 -3
index 4b821a1076..310a84729e 100644
@@ -1361,9 +1361,9 @@ mlx5_hw_proxy_port_allowed_stop(struct rte_eth_dev *dev)
 			representor_started = true;
 	}
 	if (representor_started) {
-		DRV_LOG(INFO, "Failed to stop port %u: attached representor ports"
-			      " must be stopped before stopping transfer proxy port",
-			      dev->data->port_id);
+		DRV_LOG(ERR, "Failed to stop port %u: attached representor ports"
+			     " must be stopped before stopping transfer proxy port",
+			     dev->data->port_id);
 		rte_errno = EBUSY;
 		return -rte_errno;
 	}
Signature · 1 line
2.25.1
Acked-by on v2 1/3
#6 lore raw

RE: [PATCH v2 1/3] net/mlx5: fix log level on failed transfer proxy stop

Quoted 8 lines

-----Original Message-----
From: Dariusz Sosnowski <[email protected]>
Sent: Wednesday, November 9, 2022 21:07
To: Matan Azrad <[email protected]>; Slava Ovsiienko <[email protected]>
Cc: [email protected]
Subject: [PATCH v2 1/3] net/mlx5: fix log level on failed transfer proxy stop

Quoted 8 lines

This patches increases log level for error reporting when stopping the transfer proxy port failed. Stopping can fail with EBUSY when related representor ports are still running.

Fixes 483181f7b6dd ("net/mlx5: support device control of representor

matching")

#7 lore raw

PATCH v2 2/3 doc: document E-Switch limitations with HWS in mlx5 PMD

In reply to Dariusz Sosnowski

This patch adds the following limitations to the mlx5 PMD guide:

- With HW Steering and E-Switch enabled, transfer proxy port must be started before any port representor.
- With HW Steering and E-Switch enabled, all representors must be stopped before transfer proxy port is stopped.

---
 doc/guides/nics/mlx5.rst | 13 +++++++++++++
 1 file changed, 13 insertions(+)
doc/guides/nics/mlx5.rst +13 -0
index d5f9375a4e..ca555e7ca7 100644
@@ -161,6 +161,19 @@ Limitations
   - NIC ConnectX-5 and before are not supported.
   - Partial match with item template is not supported.
   - IPv6 5-tuple matching is not supported.
+  - With E-Switch enabled, ports which share the E-Switch domain
+    should be started and stopped in a specific order:
+
+    - When starting ports, the transfer proxy port should be started first
+      and port representors should follow.
+    - When stopping ports, all of the port representors
+      should be stopped before stopping the transfer proxy port.
+
+    If ports are started/stopped in an incorrect order,
+    ``rte_eth_dev_start()``/``rte_eth_dev_stop()`` will return an appropriate error code:
+
+    - ``-EAGAIN`` for ``rte_eth_dev_start()``.
+    - ``-EBUSY`` for ``rte_eth_dev_stop()``.
 
 - When using Verbs flow engine (``dv_flow_en`` = 0), flow pattern without any
   specific VLAN will match for VLAN packets as well:
Signature · 1 line
2.25.1
Acked-by on v2 2/3
#8 lore raw

RE: [PATCH v2 2/3] doc: document E-Switch limitations with HWS in mlx5 PMD

Quoted 8 lines

-----Original Message-----
From: Dariusz Sosnowski <[email protected]>
Sent: Wednesday, November 9, 2022 21:07
To: Matan Azrad <[email protected]>; Slava Ovsiienko <[email protected]>
Cc: [email protected]
Subject: [PATCH v2 2/3] doc: document E-Switch limitations with HWS in mlx5 PMD

Quoted 8 lines

This patch adds the following limitations to the mlx5 PMD guide:

- With HW Steering and E-Switch enabled, transfer proxy port must be started before any port representor.
- With HW Steering and E-Switch enabled, all representors must be stopped before transfer proxy port is stopped.

#9 lore raw

PATCH v2 3/3 ethdev: document special cases of port start and stop

In reply to Dariusz Sosnowski

This patch clarifies the handling of following cases in the ethdev API docs:

- If rte_eth_dev_start() returns (-EAGAIN) for some port, it cannot be started until other port is started.
- If rte_eth_dev_stop() returns (-EBUSY) for some port, it cannot be stopped until other port is stopped.

When stopping the port in testpmd fails due to (-EBUSY), port's state is switched back to STARTED
to allow users to manually retry stopping the port.

No additional changes in testpmd are required to handle failure to start port with (-EAGAIN).
If rte_eth_dev_start() fails, port's state is switched to STOPPED and users are allowed to retry the operation.

---
 app/test-pmd/testpmd.c  | 10 +++++++++-
 lib/ethdev/rte_ethdev.h |  9 +++++++++
 2 files changed, 18 insertions(+), 1 deletion(-)
app/test-pmd/testpmd.c +9 -1
index aa7ea29f15..5a69e3c77a 100644
@@ -3118,6 +3118,7 @@ stop_port(portid_t pid)
 	int need_check_link_status = 0;
 	portid_t peer_pl[RTE_MAX_ETHPORTS];
 	int peer_pi;
+	int ret;
 
 	if (port_id_is_invalid(pid, ENABLED_WARN))
 		return;
@@ -3167,9 +3168,16 @@ stop_port(portid_t pid)
 		if (port->flow_list)
 			port_flow_flush(pi);
 
-		if (eth_dev_stop_mp(pi) != 0)
+		ret = eth_dev_stop_mp(pi);
+		if (ret != 0) {
 			RTE_LOG(ERR, EAL, "rte_eth_dev_stop failed for port %u\n",
 				pi);
+			if (ret == -EBUSY) {
+				/* Allow to retry stopping the port. */
+				port->port_status = RTE_PORT_STARTED;
+				continue;
+			}
+		}
 
 		if (port->port_status == RTE_PORT_HANDLING)
 			port->port_status = RTE_PORT_STOPPED;
lib/ethdev/rte_ethdev.h +9 -0
index 13fe73d5a3..abf5a24f92 100644
@@ -2701,10 +2701,14 @@ int rte_eth_dev_tx_queue_stop(uint16_t port_id, uint16_t tx_queue_id);
  * On success, all basic functions exported by the Ethernet API (link status,
  * receive/transmit, and so on) can be invoked.
  *
+ * If the port depends on another one being started,
+ * PMDs might return (-EAGAIN) to notify about such requirement.
+ *
  * @param port_id
  *   The port identifier of the Ethernet device.
  * @return
  *   - 0: Success, Ethernet device started.
+ *   - -EAGAIN: If it depends on another port to be started first.
  *   - <0: Error code of the driver device start function.
  */
 int rte_eth_dev_start(uint16_t port_id);
@@ -2713,10 +2717,15 @@ int rte_eth_dev_start(uint16_t port_id);
  * Stop an Ethernet device. The device can be restarted with a call to
  * rte_eth_dev_start()
  *
+ * If the port provides some resources for other ports
+ * and it cannot be stopped before them,
+ * PMDs might return (-EBUSY) to notify about such requirement.
+ *
  * @param port_id
  *   The port identifier of the Ethernet device.
  * @return
  *   - 0: Success, Ethernet device stopped.
+ *   - -EBUSY: If it depends on another port to be stopped first.
  *   - <0: Error code of the driver device stop function.
  */
 int rte_eth_dev_stop(uint16_t port_id);
Signature · 1 line
2.25.1
#10 lore raw
Quoted 8 lines · Dariusz Sosnowski

This patch clarifies the handling of following cases in the ethdev API docs:

- If rte_eth_dev_start() returns (-EAGAIN) for some port, it cannot be started until other port is started.
- If rte_eth_dev_stop() returns (-EBUSY) for some port, it cannot be stopped until other port is stopped.

EAGAIN and EBUSY has kind of standard meaning, I am not sure if it is good idea to change this meaning to a specific "dependency to other port" use case. Why not keep common generic meanings of the error codes?

Quoted 29 lines

When stopping the port in testpmd fails due to (-EBUSY), port's state is switched back to STARTED
to allow users to manually retry stopping the port.

No additional changes in testpmd are required to handle failure to start port with (-EAGAIN).
If rte_eth_dev_start() fails, port's state is switched to STOPPED and users are allowed to retry the operation.

---
  app/test-pmd/testpmd.c  | 10 +++++++++-
  lib/ethdev/rte_ethdev.h |  9 +++++++++
  2 files changed, 18 insertions(+), 1 deletion(-)
app/test-pmd/testpmd.c +1 -0
index aa7ea29f15..5a69e3c77a 100644
@@ -3118,6 +3118,7 @@ stop_port(portid_t pid)
  	int need_check_link_status = 0;
  	portid_t peer_pl[RTE_MAX_ETHPORTS];
  	int peer_pi;
+	int ret;
 
  	if (port_id_is_invalid(pid, ENABLED_WARN))
  		return;
@@ -3167,9 +3168,16 @@ stop_port(portid_t pid)
  		if (port->flow_list)

app/test-pmd/testpmd.c stop_port(portid_t pid) · line 3177

Quoted 10 lines
app/test-pmd/testpmd.c +5 -1
  			port_flow_flush(pi);
 
-		if (eth_dev_stop_mp(pi) != 0)
+		ret = eth_dev_stop_mp(pi);
+		if (ret != 0) {
  			RTE_LOG(ERR, EAL, "rte_eth_dev_stop failed for port %u\n",
  				pi);
+			if (ret == -EBUSY) {
+				/* Allow to retry stopping the port. */
+				port->port_status = RTE_PORT_STARTED;

If the stop() failed, isn't the current status should be STARTED independent from the error type?

Quoted 41 lines
app/test-pmd/testpmd.c +3 -0
+				continue;
+			}
+		}
 
  		if (port->port_status == RTE_PORT_HANDLING)
  			port->port_status = RTE_PORT_STOPPED;
lib/ethdev/rte_ethdev.h +9 -0
index 13fe73d5a3..abf5a24f92 100644
@@ -2701,10 +2701,14 @@ int rte_eth_dev_tx_queue_stop(uint16_t port_id, uint16_t tx_queue_id);
   * On success, all basic functions exported by the Ethernet API (link status,
   * receive/transmit, and so on) can be invoked.
   *
+ * If the port depends on another one being started,
+ * PMDs might return (-EAGAIN) to notify about such requirement.
+ *
   * @param port_id
   *   The port identifier of the Ethernet device.
   * @return
   *   - 0: Success, Ethernet device started.
+ *   - -EAGAIN: If it depends on another port to be started first.
   *   - <0: Error code of the driver device start function.
   */
  int rte_eth_dev_start(uint16_t port_id);
@@ -2713,10 +2717,15 @@ int rte_eth_dev_start(uint16_t port_id);
   * Stop an Ethernet device. The device can be restarted with a call to
   * rte_eth_dev_start()
   *
+ * If the port provides some resources for other ports
+ * and it cannot be stopped before them,
+ * PMDs might return (-EBUSY) to notify about such requirement.
+ *
   * @param port_id
   *   The port identifier of the Ethernet device.
   * @return
   *   - 0: Success, Ethernet device stopped.
+ *   - -EBUSY: If it depends on another port to be stopped first.
   *   - <0: Error code of the driver device stop function.
   */
  int rte_eth_dev_stop(uint16_t port_id);
#11 lore raw

Hi Ferruh,

Quoted 24 lines

-----Original Message-----
From: Ferruh Yigit <[email protected]>
Sent: Monday, November 14, 2022 15:08
To: Dariusz Sosnowski <[email protected]>; Aman Singh <[email protected]>; Yuying Zhang <[email protected]>; NBU-Contact-Thomas Monjalon (EXTERNAL) <[email protected]>; Andrew Rybchenko <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH v2 3/3] ethdev: document special cases of port start and stop

External email: Use caution opening links or attachments

Quoted 8 lines · Dariusz Sosnowski

This patch clarifies the handling of following cases in the ethdev API docs:

- If rte_eth_dev_start() returns (-EAGAIN) for some port, it cannot be started until other port is started.
- If rte_eth_dev_stop() returns (-EBUSY) for some port, it cannot be stopped until other port is stopped.

Quoted 4 lines

EAGAIN and EBUSY has kind of standard meaning, I am not sure if it is good idea to change this meaning to a specific "dependency to other port" use case.
Why not keep common generic meanings of the error codes?

In my opinion, using standard error meanings for EAGAIN and EBUSY would make the returned errors too vague for the API user. If we used the standard meanings, it's not clear why the port cannot be started or stopped and what the user should do about it. Providing specific reasons in the API makes it more understandable. On top of that, they are "subcases" of standard errors:

- "Port cannot be stopped because another port depends on it" is a special case of "Device or resource is busy".
- "Port cannot be started because it depends on other port being started" is a special case of "Resource temporarily unavailable".

However, I see your concern, so maybe let's do the following. To not limit the API, we could for example:

- In the documentation of returned values - provide the generic meaning for the EAGAIN and EBUSY:
- rte_eth_dev_stop(): EBUSY is returned if stopping the port is not allowed in the current state.
- rte_eth_dev_start(): EAGAIN is returned if start operation must be retried.
- In the function description provide the specific use case of "dependency on other port" as an example of EBUSY/EAGAIN usage
- Depending on the use cases emerging in the future, new examples can be added,
if EBUSY/EAGAIN is suitable for the new use cases.

What do you think?

Quoted 31 lines
Quoted 31 lines

When stopping the port in testpmd fails due to (-EBUSY), port's state is switched back to STARTED to allow users to manually retry stopping the port.

No additional changes in testpmd are required to handle failure to start port with (-EAGAIN).
If rte_eth_dev_start() fails, port's state is switched to STOPPED and users are allowed to retry the operation.

---
  app/test-pmd/testpmd.c  | 10 +++++++++-
  lib/ethdev/rte_ethdev.h |  9 +++++++++
  2 files changed, 18 insertions(+), 1 deletion(-)
app/test-pmd/testpmd.c index renamed from app/test-pmd/testpmd.c +0 -0

aa7ea29f15..5a69e3c77a 100644

app/test-pmd/testpmd.c +1 -0
@@ -3118,6 +3118,7 @@ stop_port(portid_t pid)
      int need_check_link_status = 0;
      portid_t peer_pl[RTE_MAX_ETHPORTS];
      int peer_pi;
+     int ret;
 
      if (port_id_is_invalid(pid, ENABLED_WARN))
              return;
@@ -3167,9 +3168,16 @@ stop_port(portid_t pid)
              if (port->flow_list)
                      port_flow_flush(pi);
 
Quoted 11 lines

app/test-pmd/testpmd.c stop_port(portid_t pid) · line 3177

Quoted 8 lines
app/test-pmd/testpmd.c +5 -1
-             if (eth_dev_stop_mp(pi) != 0)
+             ret = eth_dev_stop_mp(pi);
+             if (ret != 0) {
                      RTE_LOG(ERR, EAL, "rte_eth_dev_stop failed for port %u\n",
                              pi);
+                     if (ret == -EBUSY) {
+                             /* Allow to retry stopping the port. */
+                             port->port_status = RTE_PORT_STARTED;

If the stop() failed, isn't the current status should be STARTED independent from the error type?

Correct. I'll update it in v3.

Quoted 4 lines
Quoted 4 lines
app/test-pmd/testpmd.c +3 -0
+                             continue;
+                     }
+             }
 
Quoted 38 lines

lib/ethdev/rte_ethdev.h int rte_eth_dev_tx_queue_stop(uint16_t

Quoted 7 lines
app/test-pmd/testpmd.c +0 -0
              if (port->port_status == RTE_PORT_HANDLING)
                      port->port_status = RTE_PORT_STOPPED; diff --git

a/lib/ethdev/rte_ethdev.h b/lib/ethdev/rte_ethdev.h index 13fe73d5a3..abf5a24f92 100644

lib/ethdev/rte_ethdev.h +0 -0
@@ -2701,10 +2701,14 @@ int rte_eth_dev_tx_queue_stop(uint16_t

port_id, uint16_t tx_queue_id);

Quoted 30 lines
lib/ethdev/rte_ethdev.h +4 -0
   * On success, all basic functions exported by the Ethernet API (link status,
   * receive/transmit, and so on) can be invoked.
   *
+ * If the port depends on another one being started,
+ * PMDs might return (-EAGAIN) to notify about such requirement.
+ *
   * @param port_id
   *   The port identifier of the Ethernet device.
   * @return
   *   - 0: Success, Ethernet device started.
+ *   - -EAGAIN: If it depends on another port to be started first.
   *   - <0: Error code of the driver device start function.
   */
  int rte_eth_dev_start(uint16_t port_id); @@ -2713,10 +2717,15 @@ int

rte_eth_dev_start(uint16_t port_id);
* Stop an Ethernet device. The device can be restarted with a call to
* rte_eth_dev_start()
*
+ * If the port provides some resources for other ports
+ * and it cannot be stopped before them,
+ * PMDs might return (-EBUSY) to notify about such requirement.
+ *
* @param port_id
* The port identifier of the Ethernet device.
* @return
* - 0: Success, Ethernet device stopped.
+ * - -EBUSY: If it depends on another port to be stopped first.
* - <0: Error code of the driver device stop function.
*/
int rte_eth_dev_stop(uint16_t port_id);

Best regards,
Dariusz Sosnowski

#12 lore raw
Quoted 26 lines · Dariusz Sosnowski

Hi Ferruh,

Quoted 24 lines

-----Original Message-----
From: Ferruh Yigit <[email protected]>
Sent: Monday, November 14, 2022 15:08
To: Dariusz Sosnowski <[email protected]>; Aman Singh <[email protected]>; Yuying Zhang <[email protected]>; NBU-Contact-Thomas Monjalon (EXTERNAL) <[email protected]>; Andrew Rybchenko <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH v2 3/3] ethdev: document special cases of port start and stop

External email: Use caution opening links or attachments

Quoted 8 lines · Dariusz Sosnowski

This patch clarifies the handling of following cases in the ethdev API docs:

- If rte_eth_dev_start() returns (-EAGAIN) for some port, it cannot be started until other port is started.
- If rte_eth_dev_stop() returns (-EBUSY) for some port, it cannot be stopped until other port is stopped.

Quoted 9 lines
Quoted 4 lines

EAGAIN and EBUSY has kind of standard meaning, I am not sure if it is good idea to change this meaning to a specific "dependency to other port" use case.
Why not keep common generic meanings of the error codes?

In my opinion, using standard error meanings for EAGAIN and EBUSY would make the returned errors too vague for the API user. If we used the standard meanings, it's not clear why the port cannot be started or stopped and what the user should do about it. Providing specific reasons in the API makes it more understandable. On top of that, they are "subcases" of standard errors:

I think generic error meaning is not vague, although underlying reason is.

Quoted 13 lines

- "Port cannot be stopped because another port depends on it" is a special case of "Device or resource is busy".
- "Port cannot be started because it depends on other port being started" is a special case of "Resource temporarily unavailable".

However, I see your concern, so maybe let's do the following. To not limit the API, we could for example:

- In the documentation of returned values - provide the generic meaning for the EAGAIN and EBUSY:
- rte_eth_dev_stop(): EBUSY is returned if stopping the port is not allowed in the current state.
- rte_eth_dev_start(): EAGAIN is returned if start operation must be retried.
- In the function description provide the specific use case of "dependency on other port" as an example of EBUSY/EAGAIN usage
- Depending on the use cases emerging in the future, new examples can be added, if EBUSY/EAGAIN is suitable for the new use cases.

Quoted 1 line

What do you think?

OK to above generic error documentation.
And what do you think to document "dependency on other port" in the driver dev_ops function comment, since it will be an instance of the generic error message.

Quoted 92 lines
Quoted 32 lines
Quoted 32 lines

When stopping the port in testpmd fails due to (-EBUSY), port's state is switched back to STARTED to allow users to manually retry stopping the port.

No additional changes in testpmd are required to handle failure to start port with (-EAGAIN).
If rte_eth_dev_start() fails, port's state is switched to STOPPED and users are allowed to retry the operation.

---
   app/test-pmd/testpmd.c  | 10 +++++++++-
   lib/ethdev/rte_ethdev.h |  9 +++++++++
   2 files changed, 18 insertions(+), 1 deletion(-)
app/test-pmd/testpmd.c index renamed from app/test-pmd/testpmd.c +0 -0

aa7ea29f15..5a69e3c77a 100644

app/test-pmd/testpmd.c +1 -0
@@ -3118,6 +3118,7 @@ stop_port(portid_t pid)
       int need_check_link_status = 0;
       portid_t peer_pl[RTE_MAX_ETHPORTS];
       int peer_pi;
+     int ret;
 
       if (port_id_is_invalid(pid, ENABLED_WARN))
               return;
@@ -3167,9 +3168,16 @@ stop_port(portid_t pid)
               if (port->flow_list)
                       port_flow_flush(pi);
 
Quoted 11 lines

app/test-pmd/testpmd.c stop_port(portid_t pid) · line 3177

Quoted 8 lines
app/test-pmd/testpmd.c +5 -1
-             if (eth_dev_stop_mp(pi) != 0)
+             ret = eth_dev_stop_mp(pi);
+             if (ret != 0) {
                       RTE_LOG(ERR, EAL, "rte_eth_dev_stop failed for port %u\n",
                               pi);
+                     if (ret == -EBUSY) {
+                             /* Allow to retry stopping the port. */
+                             port->port_status = RTE_PORT_STARTED;

If the stop() failed, isn't the current status should be STARTED independent from the error type?

Correct. I'll update it in v3.

Quoted 4 lines
Quoted 4 lines
app/test-pmd/testpmd.c +3 -0
+                             continue;
+                     }
+             }
 
Quoted 38 lines

lib/ethdev/rte_ethdev.h int rte_eth_dev_tx_queue_stop(uint16_t

Quoted 7 lines
app/test-pmd/testpmd.c +0 -0
               if (port->port_status == RTE_PORT_HANDLING)
                       port->port_status = RTE_PORT_STOPPED; diff --git

a/lib/ethdev/rte_ethdev.h b/lib/ethdev/rte_ethdev.h index 13fe73d5a3..abf5a24f92 100644

lib/ethdev/rte_ethdev.h +0 -0
@@ -2701,10 +2701,14 @@ int rte_eth_dev_tx_queue_stop(uint16_t

port_id, uint16_t tx_queue_id);

Quoted 30 lines
lib/ethdev/rte_ethdev.h +4 -0
    * On success, all basic functions exported by the Ethernet API (link status,
    * receive/transmit, and so on) can be invoked.
    *
+ * If the port depends on another one being started,
+ * PMDs might return (-EAGAIN) to notify about such requirement.
+ *
    * @param port_id
    *   The port identifier of the Ethernet device.
    * @return
    *   - 0: Success, Ethernet device started.
+ *   - -EAGAIN: If it depends on another port to be started first.
    *   - <0: Error code of the driver device start function.
    */
   int rte_eth_dev_start(uint16_t port_id); @@ -2713,10 +2717,15 @@ int

rte_eth_dev_start(uint16_t port_id);
* Stop an Ethernet device. The device can be restarted with a call to
* rte_eth_dev_start()
*
+ * If the port provides some resources for other ports
+ * and it cannot be stopped before them,
+ * PMDs might return (-EBUSY) to notify about such requirement.
+ *
* @param port_id
* The port identifier of the Ethernet device.
* @return
* - 0: Success, Ethernet device stopped.
+ * - -EBUSY: If it depends on another port to be stopped first.
* - <0: Error code of the driver device stop function.
*/
int rte_eth_dev_stop(uint16_t port_id);

Best regards,
Dariusz Sosnowski

#13 lore raw
Quoted 78 lines

-----Original Message-----
From: Ferruh Yigit <[email protected]>
Sent: Monday, November 14, 2022 18:10
To: Dariusz Sosnowski <[email protected]>; Aman Singh <[email protected]>; Yuying Zhang <[email protected]>; NBU-Contact-Thomas Monjalon (EXTERNAL) <[email protected]>; Andrew Rybchenko <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH v2 3/3] ethdev: document special cases of port start and stop

External email: Use caution opening links or attachments

Quoted 7 lines · Dariusz Sosnowski

Hi Ferruh,

Quoted 5 lines

-----Original Message-----
From: Ferruh Yigit <[email protected]>
Sent: Monday, November 14, 2022 15:08
To: Dariusz Sosnowski <[email protected]>; Aman Singh <[email protected]>; Yuying Zhang

<[email protected]>;

Quoted 1 line
Quoted 1 line

NBU-Contact-Thomas Monjalon (EXTERNAL) <[email protected]>;

Andrew

Quoted 19 lines
Quoted 19 lines

Rybchenko <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH v2 3/3] ethdev: document special cases of port start and stop

External email: Use caution opening links or attachments

Quoted 9 lines · Dariusz Sosnowski

This patch clarifies the handling of following cases in the ethdev API
docs:

- If rte_eth_dev_start() returns (-EAGAIN) for some port, it cannot be started until other port is started.
- If rte_eth_dev_stop() returns (-EBUSY) for some port, it cannot be stopped until other port is stopped.

Quoted 6 lines
Quoted 4 lines

EAGAIN and EBUSY has kind of standard meaning, I am not sure if it is good idea to change this meaning to a specific "dependency to other port" use case.
Why not keep common generic meanings of the error codes?

In my opinion, using standard error meanings for EAGAIN and EBUSY would

make the returned errors too vague for the API user.

Quoted 1 line

If we used the standard meanings, it's not clear why the port cannot be

started or stopped and what the user should do about it.

Quoted 1 line

Providing specific reasons in the API makes it more understandable. On top

of that, they are "subcases" of standard errors:

Quoted 1 line

I think generic error meaning is not vague, although underlying reason is.

Quoted 1 line

- "Port cannot be stopped because another port depends on it" is a special

case of "Device or resource is busy".

Quoted 1 line

- "Port cannot be started because it depends on other port being started"

is a special case of "Resource temporarily unavailable".

Quoted 2 lines

However, I see your concern, so maybe let's do the following. To not limit

the API, we could for example:

Quoted 2 lines

- In the documentation of returned values - provide the generic meaning

for the EAGAIN and EBUSY:

Quoted 1 line

- rte_eth_dev_stop(): EBUSY is returned if stopping the port is not

allowed in the current state.

Quoted 1 line

- rte_eth_dev_start(): EAGAIN is returned if start operation must be

retried.

Quoted 1 line

- In the function description provide the specific use case of "dependency

on other port" as an example

Quoted 2 lines

of EBUSY/EAGAIN usage
- Depending on the use cases emerging in the future, new examples can

be added,

Quoted 8 lines
Quoted 3 lines

if EBUSY/EAGAIN is suitable for the new use cases.

What do you think?

OK to above generic error documentation.
And what do you think to document "dependency on other port" in the driver dev_ops function comment, since it will be an instance of the generic error message.

Sounds good to me. Updated in v3.

Quoted 93 lines
Quoted 44 lines
Quoted 32 lines
Quoted 32 lines

When stopping the port in testpmd fails due to (-EBUSY), port's state is switched back to STARTED to allow users to manually retry stopping the port.

No additional changes in testpmd are required to handle failure to start port with (-EAGAIN).
If rte_eth_dev_start() fails, port's state is switched to STOPPED and users are allowed to retry the operation.

---
   app/test-pmd/testpmd.c  | 10 +++++++++-
   lib/ethdev/rte_ethdev.h |  9 +++++++++
   2 files changed, 18 insertions(+), 1 deletion(-)
app/test-pmd/testpmd.c index renamed from app/test-pmd/testpmd.c +0 -0

aa7ea29f15..5a69e3c77a 100644

app/test-pmd/testpmd.c +1 -0
@@ -3118,6 +3118,7 @@ stop_port(portid_t pid)
       int need_check_link_status = 0;
       portid_t peer_pl[RTE_MAX_ETHPORTS];
       int peer_pi;
+     int ret;
 
       if (port_id_is_invalid(pid, ENABLED_WARN))
               return;
@@ -3167,9 +3168,16 @@ stop_port(portid_t pid)
               if (port->flow_list)
                       port_flow_flush(pi);
 
Quoted 11 lines

app/test-pmd/testpmd.c stop_port(portid_t pid) · line 3177

Quoted 8 lines
app/test-pmd/testpmd.c +5 -1
-             if (eth_dev_stop_mp(pi) != 0)
+             ret = eth_dev_stop_mp(pi);
+             if (ret != 0) {
                       RTE_LOG(ERR, EAL, "rte_eth_dev_stop failed for port %u\n",
                               pi);
+                     if (ret == -EBUSY) {
+                             /* Allow to retry stopping the port. */
+                             port->port_status = RTE_PORT_STARTED;

If the stop() failed, isn't the current status should be STARTED independent from the error type?

Quoted 15 lines

Correct. I'll update it in v3.

Quoted 13 lines

lib/ethdev/rte_ethdev.h int rte_eth_dev_tx_queue_stop(uint16_t

Quoted 11 lines
app/test-pmd/testpmd.c +3 -1
+                             continue;
+                     }
+             }
 
               if (port->port_status == RTE_PORT_HANDLING)
                       port->port_status = RTE_PORT_STOPPED; diff
--git a/lib/ethdev/rte_ethdev.h b/lib/ethdev/rte_ethdev.h index

13fe73d5a3..abf5a24f92 100644

lib/ethdev/rte_ethdev.h +0 -0
@@ -2701,10 +2701,14 @@ int rte_eth_dev_tx_queue_stop(uint16_t

port_id, uint16_t tx_queue_id);

Quoted 1 line
lib/ethdev/rte_ethdev.h +0 -0
    * On success, all basic functions exported by the Ethernet API (link

status,

Quoted 33 lines
Quoted 21 lines
Quoted 21 lines
lib/ethdev/rte_ethdev.h +4 -0
    * receive/transmit, and so on) can be invoked.
    *
+ * If the port depends on another one being started,
+ * PMDs might return (-EAGAIN) to notify about such requirement.
+ *
    * @param port_id
    *   The port identifier of the Ethernet device.
    * @return
    *   - 0: Success, Ethernet device started.
+ *   - -EAGAIN: If it depends on another port to be started first.
    *   - <0: Error code of the driver device start function.
    */
   int rte_eth_dev_start(uint16_t port_id); @@ -2713,10 +2717,15 @@

int rte_eth_dev_start(uint16_t port_id);
* Stop an Ethernet device. The device can be restarted with a call to
* rte_eth_dev_start()
*
+ * If the port provides some resources for other ports
+ * and it cannot be stopped before them,
+ * PMDs might return (-EBUSY) to notify about such requirement.
+ *

Quoted 8 lines
Quoted 8 lines

* @param port_id
* The port identifier of the Ethernet device.
* @return
* - 0: Success, Ethernet device stopped.
+ * - -EBUSY: If it depends on another port to be stopped first.
* - <0: Error code of the driver device stop function.
*/
int rte_eth_dev_stop(uint16_t port_id);

Best regards,
Dariusz Sosnowski

#14 lore raw

v3 cover ethdev: document special cases of port start and stop

In reply to Dariusz Sosnowski

This patch series attempts to address the special failure cases of rte_eth_dev_stop() and rte_eth_dev_start().

In case of starting a port, If the port cannot be started and start operation must be retried, PMDs might return (-EAGAIN) to notify about such situation.

In case of stopping a port, If the port cannot be stopped in the current state, PMDs might return (-EBUSY) to notify about such situation.

These cases are addressed in ethdev API docs.
Testpmd is updated to allow users to manually retry start/stop operations.

v3:
- Allow to retry port stop in testpmd for all errors.
- Made error descriptions in the API more generic and moved specific error causes descriptions to PMD.

v2:
- Fixed documentation build.

Dariusz Sosnowski (3):
net/mlx5: fix log level on failed transfer proxy stop net/mlx5: document E-Switch limitations with HWS in mlx5 PMD
ethdev: document special cases of port start and stop

 app/test-pmd/testpmd.c          |  8 +++++++-
 doc/guides/nics/mlx5.rst        | 13 +++++++++++++
 drivers/net/mlx5/mlx5_trigger.c | 17 ++++++++++++++---
 lib/ethdev/rte_ethdev.h         |  2 ++
 4 files changed, 36 insertions(+), 4 deletions(-)
Signature · 1 line
2.25.1
#15 lore raw

PATCH v3 1/3 net/mlx5: fix log level on failed transfer proxy stop

This patches increases log level for error reporting when stopping the transfer proxy port failed. Stopping can fail with EBUSY when related representor ports are still running.

Fixes 483181f7b6dd ("net/mlx5: support device control of representor matching")
---
 drivers/net/mlx5/mlx5_trigger.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/net/mlx5/mlx5_trigger.c +3 -3
index 9854df828d..fe6359908a 100644
@@ -1377,9 +1377,9 @@ mlx5_hw_proxy_port_allowed_stop(struct rte_eth_dev *dev)
 			representor_started = true;
 	}
 	if (representor_started) {
-		DRV_LOG(INFO, "Failed to stop port %u: attached representor ports"
-			      " must be stopped before stopping transfer proxy port",
-			      dev->data->port_id);
+		DRV_LOG(ERR, "Failed to stop port %u: attached representor ports"
+			     " must be stopped before stopping transfer proxy port",
+			     dev->data->port_id);
 		rte_errno = EBUSY;
 		return -rte_errno;
 	}
Signature · 1 line
2.25.1
#16 lore raw

PATCH v3 2/3 net/mlx5: document E-Switch limitations with HWS in mlx5 PMD

In reply to Dariusz Sosnowski

This patch adds the following limitations to the mlx5 PMD guide:

- With HW Steering and E-Switch enabled, transfer proxy port must be started before any port representor.
- With HW Steering and E-Switch enabled, all representors must be stopped before transfer proxy port is stopped.

Documentation of mlx5 PMD's implementations of rte_eth_dev_start() and rte_eth_dev_stop() is updated accordingly:

- rte_eth_dev_start() returns (-EAGAIN) when transfer proxy port cannot be started.
- rte_eth_dev_stop() returns (-EBUSY) when port representor cannot be stopped.

---
 doc/guides/nics/mlx5.rst        | 13 +++++++++++++
 drivers/net/mlx5/mlx5_trigger.c | 11 +++++++++++
 2 files changed, 24 insertions(+)
doc/guides/nics/mlx5.rst +13 -0
index 4f0db21dde..1df6ca9711 100644
@@ -161,6 +161,19 @@ Limitations
   - NIC ConnectX-5 and before are not supported.
   - Partial match with item template is not supported.
   - IPv6 5-tuple matching is not supported.
+  - With E-Switch enabled, ports which share the E-Switch domain
+    should be started and stopped in a specific order:
+
+    - When starting ports, the transfer proxy port should be started first
+      and port representors should follow.
+    - When stopping ports, all of the port representors
+      should be stopped before stopping the transfer proxy port.
+
+    If ports are started/stopped in an incorrect order,
+    ``rte_eth_dev_start()``/``rte_eth_dev_stop()`` will return an appropriate error code:
+
+    - ``-EAGAIN`` for ``rte_eth_dev_start()``.
+    - ``-EBUSY`` for ``rte_eth_dev_stop()``.
 
 - When using Verbs flow engine (``dv_flow_en`` = 0), flow pattern without any
   specific VLAN will match for VLAN packets as well:
drivers/net/mlx5/mlx5_trigger.c +11 -0
index fe6359908a..f54443ed1a 100644
@@ -1138,6 +1138,10 @@ mlx5_hw_representor_port_allowed_start(struct rte_eth_dev *dev)
  *
  * @return
  *   0 on success, a negative errno value otherwise and rte_errno is set.
+ *   The following error values are defined:
+ *
+ *   - -EAGAIN: If port representor cannot be started,
+ *     because transfer proxy port is not started.
  */
 int
 mlx5_dev_start(struct rte_eth_dev *dev)
@@ -1394,6 +1398,13 @@ mlx5_hw_proxy_port_allowed_stop(struct rte_eth_dev *dev)
  *
  * @param dev
  *   Pointer to Ethernet device structure.
+ *
+ * @return
+ *   0 on success, a negative errno value otherwise and rte_errno is set.
+ *   The following error values are defined:
+ *
+ *   - -EBUSY: If transfer proxy port cannot be stopped,
+ *     because other port representors are still running.
  */
 int
 mlx5_dev_stop(struct rte_eth_dev *dev)
Signature · 1 line
2.25.1
Acked-by on v3 2/3
#17 lore raw

RE: [PATCH v3 2/3] net/mlx5: document E-Switch limitations with HWS in mlx5 PMD

Quoted 18 lines

-----Original Message-----
From: Dariusz Sosnowski <[email protected]>
Sent: Monday, November 14, 2022 20:20
To: Matan Azrad <[email protected]>; Slava Ovsiienko <[email protected]>
Cc: [email protected]
Subject: [PATCH v3 2/3] net/mlx5: document E-Switch limitations with HWS in mlx5 PMD

This patch adds the following limitations to the mlx5 PMD guide:

- With HW Steering and E-Switch enabled, transfer proxy port must be started before any port representor.
- With HW Steering and E-Switch enabled, all representors must be stopped before transfer proxy port is stopped.

Documentation of mlx5 PMD's implementations of rte_eth_dev_start() and rte_eth_dev_stop() is updated accordingly:

Quoted 6 lines

- rte_eth_dev_start() returns (-EAGAIN) when transfer proxy port cannot be started.
- rte_eth_dev_stop() returns (-EBUSY) when port representor cannot be stopped.

#18 lore raw

PATCH v3 3/3 ethdev: document special cases of port start and stop

In reply to Dariusz Sosnowski

This patch clarifies the handling of following cases in the ethdev API docs:

- If rte_eth_dev_start() returns (-EAGAIN) for some port, it cannot be started right now and start operation must be retried.
- If rte_eth_dev_stop() returns (-EBUSY) for some port, it cannot be stopped in the current state.

When stopping the port in testpmd fails, port's state is switched back to STARTED
to allow users to manually retry stopping the port.

No additional changes in testpmd are required to handle failures to start the port.
If rte_eth_dev_start() fails, port's state is switched to STOPPED and users are allowed to retry the operation.

---
 app/test-pmd/testpmd.c  | 8 +++++++-
 lib/ethdev/rte_ethdev.h | 2 ++
 2 files changed, 9 insertions(+), 1 deletion(-)
app/test-pmd/testpmd.c +7 -1
index 4e25f77c6a..a0b4ede48b 100644
@@ -3182,6 +3182,7 @@ stop_port(portid_t pid)
 	int need_check_link_status = 0;
 	portid_t peer_pl[RTE_MAX_ETHPORTS];
 	int peer_pi;
+	int ret;
 
 	if (port_id_is_invalid(pid, ENABLED_WARN))
 		return;
@@ -3231,9 +3232,14 @@ stop_port(portid_t pid)
 		if (port->flow_list)
 			port_flow_flush(pi);
 
-		if (eth_dev_stop_mp(pi) != 0)
+		ret = eth_dev_stop_mp(pi);
+		if (ret != 0) {
 			RTE_LOG(ERR, EAL, "rte_eth_dev_stop failed for port %u\n",
 				pi);
+			/* Allow to retry stopping the port. */
+			port->port_status = RTE_PORT_STARTED;
+			continue;
+		}
 
 		if (port->port_status == RTE_PORT_HANDLING)
 			port->port_status = RTE_PORT_STOPPED;
lib/ethdev/rte_ethdev.h +2 -0
index 13fe73d5a3..c129ca1eaf 100644
@@ -2705,6 +2705,7 @@ int rte_eth_dev_tx_queue_stop(uint16_t port_id, uint16_t tx_queue_id);
  *   The port identifier of the Ethernet device.
  * @return
  *   - 0: Success, Ethernet device started.
+ *   - -EAGAIN: If start operation must be retried.
  *   - <0: Error code of the driver device start function.
  */
 int rte_eth_dev_start(uint16_t port_id);
@@ -2717,6 +2718,7 @@ int rte_eth_dev_start(uint16_t port_id);
  *   The port identifier of the Ethernet device.
  * @return
  *   - 0: Success, Ethernet device stopped.
+ *   - -EBUSY: If stopping the port is not allowed in current state.
  *   - <0: Error code of the driver device stop function.
  */
 int rte_eth_dev_stop(uint16_t port_id);
Signature · 1 line
2.25.1
Acked-by on v3 3/3
#19 lore raw
Quoted 13 lines · Dariusz Sosnowski

This patch clarifies the handling of following cases in the ethdev API docs:

- If rte_eth_dev_start() returns (-EAGAIN) for some port, it cannot be started right now and start operation must be retried.
- If rte_eth_dev_stop() returns (-EBUSY) for some port, it cannot be stopped in the current state.

When stopping the port in testpmd fails, port's state is switched back to STARTED
to allow users to manually retry stopping the port.

Quoted 6 lines

No additional changes in testpmd are required to handle failures to start the port.
If rte_eth_dev_start() fails, port's state is switched to STOPPED and users are allowed to retry the operation.

#20 lore raw
In reply to Dariusz Sosnowski
Quoted 4 lines

Dariusz Sosnowski (3):
net/mlx5: fix log level on failed transfer proxy stop net/mlx5: document E-Switch limitations with HWS in mlx5 PMD
ethdev: document special cases of port start and stop

There is a change in testpmd but it looks simple enough for -rc4. Applied, thanks.