From: Jingjing Wu <jingjing.wu@intel.com>
To: dev@dpdk.org
Cc: jingjing.wu@intel.com, jerinj@marvell.com,
pbhagavatula@marvell.com, zhirun.yan@intel.com
Subject: [PATCH v2] graph: fix head move when graph walk in mcore dispatch
Date: Fri, 22 Mar 2024 15:46:37 +0000 [thread overview]
Message-ID: <20240322154637.1346239-1-jingjing.wu@intel.com> (raw)
In-Reply-To: <20240319141454.3275543-1-jingjing.wu@intel.com>
Head move happens before the core id check, which will cause the last
source node be executed even core id is not correct. This patch changes
head check to less than 1 instead of 0 to fix this issue.
Fixes: 35dfd9b9fd85 ("graph: introduce graph walk by cross-core dispatch")
Signed-off-by: Jingjing Wu <jingjing.wu@intel.com>
---
lib/graph/rte_graph_model_mcore_dispatch.h | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/lib/graph/rte_graph_model_mcore_dispatch.h b/lib/graph/rte_graph_model_mcore_dispatch.h
index 75ec388cad..1cc75b7ac4 100644
--- a/lib/graph/rte_graph_model_mcore_dispatch.h
+++ b/lib/graph/rte_graph_model_mcore_dispatch.h
@@ -100,9 +100,8 @@ rte_graph_walk_mcore_dispatch(struct rte_graph *graph)
node = (struct rte_node *)RTE_PTR_ADD(graph, cir_start[(int32_t)head++]);
/* skip the src nodes which not bind with current worker */
- if ((int32_t)head < 0 && node->dispatch.lcore_id != graph->dispatch.lcore_id)
+ if ((int32_t)head < 1 && node->dispatch.lcore_id != graph->dispatch.lcore_id)
continue;
-
/* Schedule the node until all task/objs are done */
if (node->dispatch.lcore_id != RTE_MAX_LCORE &&
graph->dispatch.lcore_id != node->dispatch.lcore_id &&
--
2.34.1
next prev parent reply other threads:[~2024-03-22 7:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 14:14 [PATCH] " Jingjing Wu
2024-03-20 3:33 ` Yan, Zhirun
2024-03-20 6:25 ` Wu, Jingjing
2024-03-20 8:42 ` Yan, Zhirun
2024-03-21 3:39 ` Wu, Jingjing
2024-03-21 5:34 ` Yan, Zhirun
2024-03-22 15:46 ` Jingjing Wu [this message]
2024-03-28 8:32 ` [PATCH v2] " Yan, Zhirun
2024-06-27 13:52 ` Thomas Monjalon
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=20240322154637.1346239-1-jingjing.wu@intel.com \
--to=jingjing.wu@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=zhirun.yan@intel.com \
/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).