|WARNING| pw123958 [PATCH] [v3] net/mlx5: support live migration

[dpdklab at iol.unh.edu]

Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/123958

_apply patch failure_

Submitter: Rongwei Liu <rongweil at nvidia.com>
Date: Wednesday, February 15 2023 12:03:45 
Applied on: CommitID:04ed18cd41f12ea1487581731ef56185d902d827
Apply patch set 123958 failed:

Checking patch doc/guides/nics/mlx5.rst...
error: while searching for:
- When using DV/verbs flow engine (``dv_flow_en`` = 1/0 respectively), Match on SPI field
  in ESP header for group 0 needs MLNX_OFED 5.6+.


Statistics
----------

error: patch failed: doc/guides/nics/mlx5.rst:612
Checking patch drivers/net/mlx5/mlx5.h...
Hunk #2 succeeded at 1642 (offset -15 lines).
Hunk #3 succeeded at 1771 (offset -15 lines).
Checking patch drivers/net/mlx5/mlx5_flow.c...
Hunk #2 succeeded at 7381 (offset -106 lines).
Hunk #3 succeeded at 7643 (offset -106 lines).
Hunk #4 succeeded at 7668 (offset -106 lines).
Hunk #5 succeeded at 7740 (offset -106 lines).
Hunk #6 succeeded at 7753 (offset -106 lines).
Hunk #7 succeeded at 8216 (offset -106 lines).
Hunk #8 succeeded at 8226 (offset -106 lines).
Checking patch drivers/net/mlx5/rte_pmd_mlx5.h...
Checking patch drivers/net/mlx5/version.map...
Applying patch doc/guides/nics/mlx5.rst with 1 reject...
Rejected hunk #1.
Applied patch drivers/net/mlx5/mlx5.h cleanly.
Applied patch drivers/net/mlx5/mlx5_flow.c cleanly.
Applied patch drivers/net/mlx5/rte_pmd_mlx5.h cleanly.
Applied patch drivers/net/mlx5/version.map cleanly.
diff a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst	(rejected hunks)
@@ -612,6 +612,14 @@ Limitations
 - When using DV/verbs flow engine (``dv_flow_en`` = 1/0 respectively), Match on SPI field
   in ESP header for group 0 needs MLNX_OFED 5.6+.
 
+- During live migration to a new process set its flow engine as standby mode,
+  the user should only program flow rules in group 0 (``fdb_def_rule_en=0``).
+  Live migration is only supported under SWS (``dv_flow_en=1``).
+  The flow group 0 is shared between DPDK processes
+  while the other flow groups are limited to the current process.
+  The flow engine of a process cannot move from active to standby mode
+  if preceding active application rules are still present and vice versa.
+
 
 Statistics
 ----------

https://lab.dpdk.org/results/dashboard/patchsets/25410/

UNH-IOL DPDK Community Lab