From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Dariusz Sosnowski <dsosnowski@nvidia.com>, zhoumin@loongson.cn
Subject: |WARNING| pw152105-152103 [PATCH v3 1/3] net/mlx5/hws: support jump FDB Rx
Date: Wed, 26 Feb 2025 23:30:32 +0800 [thread overview]
Message-ID: <202502261530.51QFUWLN3039839@localhost.localdomain> (raw)
In-Reply-To: <20250226160425.78147-2-dsosnowski@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/152105
_apply patch failure_
Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Wed, 26 Feb 2025 17:04:23 +0100
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: bc515897cc31bbcc12792bdc5064b8395c9b75d8
Apply patch set 152105-152103 failed:
Checking patch drivers/common/mlx5/mlx5_devx_cmds.c...
error: while searching for:
attr->fdb_unified_en = MLX5_GET(wqe_based_flow_table_cap,
hcattr,
fdb_unified_en);
}
/* Query HCA attribute for ROCE. */
if (attr->roce) {
error: patch failed: drivers/common/mlx5/mlx5_devx_cmds.c:1352
error: drivers/common/mlx5/mlx5_devx_cmds.c: patch does not apply
Checking patch drivers/common/mlx5/mlx5_devx_cmds.h...
error: while searching for:
uint32_t lag_rx_port_affinity:1;
uint32_t wqe_based_flow_table_sup:1;
uint32_t fdb_unified_en:1;
uint8_t max_header_modify_pattern_length;
uint64_t system_image_guid;
uint32_t log_max_conn_track_offload:5;
error: patch failed: drivers/common/mlx5/mlx5_devx_cmds.h:326
error: drivers/common/mlx5/mlx5_devx_cmds.h: patch does not apply
Checking patch drivers/net/mlx5/linux/mlx5_os.c...
error: while searching for:
* 4. all representors in HWS
*/
priv->unified_fdb_en = !!priv->master && sh->cdev->config.hca_attr.fdb_unified_en;
DRV_LOG(DEBUG, "port %u: unified FDB %s enabled.",
eth_dev->data->port_id, priv->unified_fdb_en ? "is" : "isn't");
if (priv->sh->config.dv_esw_en) {
uint32_t usable_bits;
uint32_t required_bits;
error: patch failed: drivers/net/mlx5/linux/mlx5_os.c:1716
error: drivers/net/mlx5/linux/mlx5_os.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5.h...
error: while searching for:
uint32_t num_lag_ports:4; /* Number of ports can be bonded. */
uint32_t tunnel_enabled:1; /* If tunnel offloading is enabled on rxqs. */
uint32_t unified_fdb_en:1; /* Unified FDB flag per port. */
uint16_t domain_id; /* Switch domain identifier. */
uint16_t vport_id; /* Associated VF vport index (if any). */
uint32_t vport_meta_tag; /* Used for vport index match ove VF LAG. */
error: patch failed: drivers/net/mlx5/mlx5.h:1987
error: drivers/net/mlx5/mlx5.h: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow_hw.c...
Hunk #1 succeeded at 9248 (offset -102 lines).
error: while searching for:
goto error;
grp_data->tbl = tbl;
if (attr->group) {
/* Jump action be used by non-root table. */
jump = mlx5dr_action_create_dest_table
(priv->dr_ctx, tbl,
mlx5_hw_act_dest_table_flag[dr_tbl_attr.type]);
if (!jump)
goto error;
grp_data->jump.hws_action = jump;
error: patch failed: drivers/net/mlx5/mlx5_flow_hw.c:9370
error: drivers/net/mlx5/mlx5_flow_hw.c: patch does not apply
next parent reply other threads:[~2025-02-26 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250226160425.78147-2-dsosnowski@nvidia.com>
2025-02-26 15:30 ` qemudev [this message]
2025-02-26 16:07 ` |SUCCESS| pw152105 " 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=202502261530.51QFUWLN3039839@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=dsosnowski@nvidia.com \
--cc=test-report@dpdk.org \
--cc=zhoumin@loongson.cn \
/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).