From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw68648[v2, 02/10] net/mlx5: optimize action flags in flow handle
Date: 16 Apr 2020 17:04:53 -0700 [thread overview]
Message-ID: <fecc85$9tj3m5@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3056 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/68648
_apply issues_
Submitter: Suanming Mou <suanmingm@mellanox.com>
Date: 2020-04-16 08:34:23
Reply_mail: 1587026071-422636-3-git-send-email-suanmingm@mellanox.com
DPDK git baseline:
Repo:dpdk-next-net-mlx, CommitID: 5bcd77844fb59cf4546defd455ef4b653a9ed6ae
Repo:dpdk, CommitID: c3eb8b62744930029f96c5d64d9adac5749908ef
*Repo: dpdk-next-net-mlx
/**< Index to port ID action resource. */
};
#ifdef HAVE_IBV_FLOW_DV_SUPPORT
struct mlx5_flow_handle_dv dvh;
error: patch failed: drivers/net/mlx5/mlx5_flow.h:502
error: drivers/net/mlx5/mlx5_flow.h: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow_dv.c...
error: while searching for:
dev_flow->dv.actions[actions_n++] =
dev_flow->dv.port_id_action->action;
--
action_flags |= MLX5_FLOW_ACTION_FLAG;
if (dev_conf->dv_xmeta_en != MLX5_XMETA_MODE_LEGACY) {
struct rte_flow_action_mark mark = {
.id = MLX5_FLOW_MARK_DEFAULT,
error: patch failed: drivers/net/mlx5/mlx5_flow_dv.c:7445
error: drivers/net/mlx5/mlx5_flow_dv.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow_verbs.c...
Hunk #1 succeeded at 1586 (offset -3 lines).
Hunk #2 succeeded at 1623 (offset -3 lines).
error: while searching for:
--
MLX5_FLOW_ACTION_RSS)) {
mlx5_hrxq_release(dev, handle->hrxq);
handle->hrxq = 0;
}
error: patch failed: drivers/net/mlx5/mlx5_flow_verbs.c:1756
error: drivers/net/mlx5/mlx5_flow_verbs.c: patch does not apply
*Repo: dpdk
(MLX5_FLOW_ACTION_FLAG | MLX5_FLOW_ACTION_MARK));
const int tunnel = !!(dev_handle->layers & MLX5_FLOW_LAYER_TUNNEL);
unsigned int i;
error: patch failed: drivers/net/mlx5/mlx5_flow.c:722
error: drivers/net/mlx5/mlx5_flow.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow.h...
error: while searching for:
/**< Index to next device flow handle. */
uint64_t layers;
--
/**< Index to port ID action resource. */
};
#ifdef HAVE_IBV_FLOW_DV_SUPPORT
struct mlx5_flow_handle_dv dvh;
error: patch failed: drivers/net/mlx5/mlx5_flow.h:502
error: drivers/net/mlx5/mlx5_flow.h: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow_dv.c...
error: while searching for:
dev_flow->dv.actions[actions_n++] =
dev_flow->dv.port_id_action->action;
--
action_flags |= MLX5_FLOW_ACTION_FLAG;
if (dev_conf->dv_xmeta_en != MLX5_XMETA_MODE_LEGACY) {
struct rte_flow_action_mark mark = {
.id = MLX5_FLOW_MARK_DEFAULT,
error: patch failed: drivers/net/mlx5/mlx5_flow_dv.c:7445
error: drivers/net/mlx5/mlx5_flow_dv.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow_verbs.c...
Hunk #1 succeeded at 1466 (offset -123 lines).
error: while searching for:
"action not supported");
--
dev_flow->handle->act_flags = action_flags;
for (; items->type != RTE_FLOW_ITEM_TYPE_END; items++) {
int tunnel = !!(item_flags & MLX5_FLOW_LAYER_TUNNEL);
error: patch failed: drivers/net/mlx5/mlx5_flow_verbs.c:1621
error: drivers/net/mlx5/mlx5_flow_verbs.c: patch does not apply
DPDK STV team
reply other threads:[~2020-04-17 0:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='fecc85$9tj3m5@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--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).