From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw123958 [PATCH] [v3] net/mlx5: support live migration
Date: Wed, 15 Feb 2023 07:19:02 -0500 (EST) [thread overview]
Message-ID: <20230215121902.682244AC@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2312 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/123958
_apply patch failure_
Submitter: Rongwei Liu <rongweil@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
next reply other threads:[~2023-02-15 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 12:19 dpdklab [this message]
[not found] <20230215120345.3928888-1-rongweil@nvidia.com>
2023-02-15 12:05 ` |WARNING| pw123958 [PATCH v3] " checkpatch
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=20230215121902.682244AC@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
/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).