From: Zhirun Yan <zhirun.yan@intel.com>
To: dev@dpdk.org, jerinj@marvell.com, kirankumark@marvell.com
Cc: cunming.liang@intel.com, haiyue.wang@intel.com,
Zhirun Yan <zhirun.yan@intel.com>
Subject: [RFC, v1 0/6] graph enhancement for multi-core dispatch
Date: Thu, 8 Sep 2022 10:09:53 +0800 [thread overview]
Message-ID: <20220908020959.1675953-1-zhirun.yan@intel.com> (raw)
Currently, the rte_graph_walk() and rte_node_enqueue* fast path API
functions in graph lib implementation are designed to work on single-core.
This solution(RFC) proposes usage of cross-core dispatching mechanism to
enhance the graph scaling strategy. We introduce Scheduler Workqueue
then we could directly dispatch streams to another worker core which is
affinity with a specific node.
This RFC：
1. Introduce core affinity API and graph clone API.
2. Introduce key functions to enqueue/dequeue for dispatching streams.
3. Enhance rte_graph_walk by cross-core dispatch.
4. Add l2fwd-graph example and stats for cross-core dispatching.
With this patch set, it could easily plan and orchestrate stream on
multi-core systems.
Future work:
1. Support to affinity lcore set for one node.
2. Use l3fwd-graph instead of l2fwd-graph as example in patch 06.
3. Add new parameter, like --node(nodeid, lcoreid) to config node for core
affinity.
Comments and suggestions are welcome. Thanks!
Haiyue Wang (1):
examples: add l2fwd-graph
Zhirun Yan (5):
graph: introduce core affinity API into graph
graph: introduce graph clone API for other worker core
graph: enable stream moving cross cores
graph: enhance graph walk by cross-core dispatch
graph: add stats for corss-core dispatching
examples/l2fwd-graph/main.c | 455 +++++++++++++++++++++++++++++++
examples/l2fwd-graph/meson.build | 25 ++
examples/l2fwd-graph/node.c | 263 ++++++++++++++++++
examples/l2fwd-graph/node.h | 64 +++++
examples/meson.build | 1 +
lib/graph/graph.c | 121 ++++++++
lib/graph/graph_debug.c | 4 +
lib/graph/graph_populate.c | 1 +
lib/graph/graph_private.h | 43 +++
lib/graph/graph_sched.c | 194 +++++++++++++
lib/graph/graph_stats.c | 19 +-
lib/graph/meson.build | 2 +
lib/graph/node.c | 25 ++
lib/graph/rte_graph.h | 50 ++++
lib/graph/rte_graph_worker.h | 59 ++++
lib/graph/version.map | 5 +
16 files changed, 1327 insertions(+), 4 deletions(-)
create mode 100644 examples/l2fwd-graph/main.c
create mode 100644 examples/l2fwd-graph/meson.build
create mode 100644 examples/l2fwd-graph/node.c
create mode 100644 examples/l2fwd-graph/node.h
create mode 100644 lib/graph/graph_sched.c
--
2.25.1
next reply other threads:[~2022-09-08 2:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 2:09 Zhirun Yan [this message]
2022-09-08 2:09 ` [RFC, v1 1/6] graph: introduce core affinity API into graph Zhirun Yan
2022-09-08 2:09 ` [RFC, v1 2/6] graph: introduce graph clone API for other worker core Zhirun Yan
2022-09-08 2:09 ` [RFC, v1 3/6] graph: enable stream moving cross cores Zhirun Yan
2022-09-08 2:09 ` [RFC, v1 4/6] graph: enhance graph walk by cross-core dispatch Zhirun Yan
2022-09-08 5:27 ` [EXT] " Pavan Nikhilesh Bhagavatula
2022-09-15 1:52 ` Yan, Zhirun
2022-09-08 2:09 ` [RFC, v1 5/6] graph: add stats for corss-core dispatching Zhirun Yan
2022-09-08 2:09 ` [RFC, v1 6/6] examples: add l2fwd-graph Zhirun Yan
2022-09-20 9:33 ` [RFC, v1 0/6] graph enhancement for multi-core dispatch Jerin Jacob
2022-09-30 6:41 ` Yan, Zhirun
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=20220908020959.1675953-1-zhirun.yan@intel.com \
--to=zhirun.yan@intel.com \
--cc=cunming.liang@intel.com \
--cc=dev@dpdk.org \
--cc=haiyue.wang@intel.com \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.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).