Cover Detail
Show a cover letter.
GET /api/covers/125616/?format=api
{ "id": 125616, "url": "http://patches.dpdk.org/api/covers/125616/?format=api", "web_url": "http://patches.dpdk.org/project/dpdk/cover/20230330061834.3118201-1-zhirun.yan@intel.com/", "project": { "id": 1, "url": "http://patches.dpdk.org/api/projects/1/?format=api", "name": "DPDK", "link_name": "dpdk", "list_id": "dev.dpdk.org", "list_email": "dev@dpdk.org", "web_url": "http://core.dpdk.org", "scm_url": "git://dpdk.org/dpdk", "webscm_url": "http://git.dpdk.org/dpdk", "list_archive_url": "https://inbox.dpdk.org/dev", "list_archive_url_format": "https://inbox.dpdk.org/dev/{}", "commit_url_format": "" }, "msgid": "<20230330061834.3118201-1-zhirun.yan@intel.com>", "list_archive_url": "https://inbox.dpdk.org/dev/20230330061834.3118201-1-zhirun.yan@intel.com", "date": "2023-03-30T06:18:19", "name": "[v4,00/15] graph enhancement for multi-core dispatch", "submitter": { "id": 1154, "url": "http://patches.dpdk.org/api/people/1154/?format=api", "name": "Yan, Zhirun", "email": "zhirun.yan@intel.com" }, "mbox": "http://patches.dpdk.org/project/dpdk/cover/20230330061834.3118201-1-zhirun.yan@intel.com/mbox/", "series": [ { "id": 27579, "url": "http://patches.dpdk.org/api/series/27579/?format=api", "web_url": "http://patches.dpdk.org/project/dpdk/list/?series=27579", "date": "2023-03-30T06:18:19", "name": "graph enhancement for multi-core dispatch", "version": 4, "mbox": "http://patches.dpdk.org/series/27579/mbox/" } ], "comments": "http://patches.dpdk.org/api/covers/125616/comments/", "headers": { "Return-Path": "<dev-bounces@dpdk.org>", "X-Original-To": "patchwork@inbox.dpdk.org", "Delivered-To": "patchwork@inbox.dpdk.org", "Received": [ "from mails.dpdk.org (mails.dpdk.org [217.70.189.124])\n\tby inbox.dpdk.org (Postfix) with ESMTP id E415C4286D;\n\tThu, 30 Mar 2023 08:18:45 +0200 (CEST)", "from mails.dpdk.org (localhost [127.0.0.1])\n\tby mails.dpdk.org (Postfix) with ESMTP id 8E17D40E5A;\n\tThu, 30 Mar 2023 08:18:44 +0200 (CEST)", "from mga03.intel.com (mga03.intel.com [134.134.136.65])\n by mails.dpdk.org (Postfix) with ESMTP id D191940685\n for <dev@dpdk.org>; Thu, 30 Mar 2023 08:18:42 +0200 (CEST)", "from fmsmga001.fm.intel.com ([10.253.24.23])\n by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384;\n 29 Mar 2023 23:18:40 -0700", "from dpdk-zhirun-lmm.sh.intel.com ([10.67.119.68])\n by fmsmga001.fm.intel.com with ESMTP; 29 Mar 2023 23:18:38 -0700" ], "DKIM-Signature": "v=1; a=rsa-sha256; c=relaxed/simple;\n d=intel.com; i=@intel.com; q=dns/txt; s=Intel;\n t=1680157123; x=1711693123;\n h=from:to:cc:subject:date:message-id:in-reply-to:\n references:mime-version:content-transfer-encoding;\n bh=k49gFNlWov1LP8paZBuO/6o0oS+jhjyide5iCyJdf38=;\n b=i+feCcWHHxuGLAbp0EgxYdlskWBvqliII54sZlT3CC0ThSqS/7p7rnYf\n H813tt9eQQjDVbhwZusivv0uaM3aTf8tgEIfXtw6OdoQGoB/+x9SoxFUY\n gUzkoWyfs5gbLU3KFbN1zIv/KalR///0zBhvWR3pREkyiEjx+2cRNxGdb\n Bw2j01QnZD56KhEu7A+byCei0ZhwDxOr+ufF4eDyNzdeC1I13laALPIdB\n CaO5mg3SW6Jybz/OT3pEUry33NXp2HRXBBLp4OdNBfBw35aVOR1b8Naen\n QL3hJequmT1xbB6+5PIYxnWZx9Hw2D3nMAgwun7/dePSlG10GRAKJ3Pv8 g==;", "X-IronPort-AV": [ "E=McAfee;i=\"6600,9927,10664\"; a=\"343530549\"", "E=Sophos;i=\"5.98,303,1673942400\"; d=\"scan'208\";a=\"343530549\"", "E=McAfee;i=\"6600,9927,10664\"; a=\"828176149\"", "E=Sophos;i=\"5.98,303,1673942400\"; d=\"scan'208\";a=\"828176149\"" ], "X-ExtLoop1": "1", "From": "Zhirun Yan <zhirun.yan@intel.com>", "To": "dev@dpdk.org, jerinj@marvell.com, kirankumark@marvell.com,\n ndabilpuram@marvell.com", "Cc": "cunming.liang@intel.com, haiyue.wang@intel.com,\n Zhirun Yan <zhirun.yan@intel.com>", "Subject": "[PATCH v4 00/15] graph enhancement for multi-core dispatch", "Date": "Thu, 30 Mar 2023 15:18:19 +0900", "Message-Id": "<20230330061834.3118201-1-zhirun.yan@intel.com>", "X-Mailer": "git-send-email 2.37.2", "In-Reply-To": "<20230329064340.2550530-1-zhirun.yan@intel.com>", "References": "<20230329064340.2550530-1-zhirun.yan@intel.com>", "MIME-Version": "1.0", "Content-Transfer-Encoding": "8bit", "X-BeenThere": "dev@dpdk.org", "X-Mailman-Version": "2.1.29", "Precedence": "list", "List-Id": "DPDK patches and discussions <dev.dpdk.org>", "List-Unsubscribe": "<https://mails.dpdk.org/options/dev>,\n <mailto:dev-request@dpdk.org?subject=unsubscribe>", "List-Archive": "<http://mails.dpdk.org/archives/dev/>", "List-Post": "<mailto:dev@dpdk.org>", "List-Help": "<mailto:dev-request@dpdk.org?subject=help>", "List-Subscribe": "<https://mails.dpdk.org/listinfo/dev>,\n <mailto:dev-request@dpdk.org?subject=subscribe>", "Errors-To": "dev-bounces@dpdk.org" }, "content": "V4:\nFix CI build issues about undefined reference of sched apis.\nRemove inline for model setting.\n\nV3:\nFix CI build issues about TLS and typo.\n\nV2:\nUse git mv to keep git history.\nUse TLS for per-thread local storage.\nChange model name to mcore dispatch.\nChange API with specific mode name.\nSplit big patch.\nFix CI issues.\nRebase l3fwd-graph example.\nUpdate doc and maintainers files.\n\n\nCurrently, rte_graph supports RTC (Run-To-Completion) model within each\nof a single core.\nRTC is one of the typical model of packet processing. Others like\nPipeline or Hybrid are lack of support.\n\nThe patch set introduces a 'multicore dispatch' model selection which\nis a self-reacting scheme according to the core affinity.\nThe new model enables a cross-core dispatching mechanism which employs a\nscheduling work-queue to dispatch streams to other worker cores which\nbeing associated with the destination node. When core flavor of the\ndestination node is a default 'current', the stream can be continue\nexecuted as normal.\n\nExample:\n3-node graph targets 3-core budget\n\nRTC:\nGraph: node-0 -> node-1 -> node-2 @Core0.\n\n+ - - - - - - - - - - - - - - - - - - - - - +\n' Core #0/1/2 '\n' '\n' +--------+ +---------+ +--------+ '\n' | Node-0 | --> | Node-1 | --> | Node-2 | '\n' +--------+ +---------+ +--------+ '\n' '\n+ - - - - - - - - - - - - - - - - - - - - - +\n\nDispatch:\n\nGraph topo: node-0 -> Core1; node-1 -> node-2; node-2 -> node-3.\nConfig graph: node-0 @Core0; node-1/3 @Core1; node-2 @Core2.\n\n.. code-block:: diff\n\n + - - - - - -+ +- - - - - - - - - - - - - + + - - - - - -+\n ' Core #0 ' ' Core #1 ' ' Core #2 '\n ' ' ' ' ' '\n ' +--------+ ' ' +--------+ +--------+ ' ' +--------+ '\n ' | Node-0 | - - - ->| Node-1 | | Node-3 |<- - - - | Node-2 | '\n ' +--------+ ' ' +--------+ +--------+ ' ' +--------+ '\n ' ' ' | ' ' ^ '\n + - - - - - -+ +- - -|- - - - - - - - - - + + - - -|- - -+\n | |\n + - - - - - - - - - - - - - - - - +\n\n\nThe patch set has been break down as below:\n\n1. Split graph worker into common and default model part.\n2. Inline graph node processing to make it reusable.\n3. Add set/get APIs to choose worker model.\n4. Introduce core affinity API to set the node run on specific worker core.\n (only use in new model)\n5. Introduce graph affinity API to bind one graph with specific worker\n core.\n6. Introduce graph clone API.\n7. Introduce stream moving with scheduler work-queue in patch 8~12.\n8. Add stats for new models.\n9. Abstract default graph config process and integrate new model into\n example/l3fwd-graph. Add new parameters for model choosing.\n\nWe could run with new worker model by this:\n./dpdk-l3fwd-graph -l 8,9,10,11 -n 4 -- -p 0x1 --config=\"(0,0,9)\" -P\n--model=\"dispatch\"\n\nReferences:\nhttps://static.sched.com/hosted_files/dpdkuserspace22/a6/graph%20introduce%20remote%20dispatch%20for%20mult-core%20scaling.pdf\n\n\nZhirun Yan (15):\n graph: rename rte_graph_work as common\n graph: split graph worker into common and default model\n graph: move node process into inline function\n graph: add get/set graph worker model APIs\n graph: introduce graph node core affinity API\n graph: introduce graph bind unbind API\n graph: introduce graph clone API for other worker core\n graph: add struct for stream moving between cores\n graph: introduce stream moving cross cores\n graph: enable create and destroy graph scheduling workqueue\n graph: introduce graph walk by cross-core dispatch\n graph: enable graph multicore dispatch scheduler model\n graph: add stats for cross-core dispatching\n examples/l3fwd-graph: introduce multicore dispatch worker model\n doc: update multicore dispatch model in graph guides\n\n MAINTAINERS | 1 +\n doc/guides/prog_guide/graph_lib.rst | 59 ++-\n examples/l3fwd-graph/main.c | 237 +++++++++---\n lib/graph/graph.c | 179 +++++++++\n lib/graph/graph_debug.c | 6 +\n lib/graph/graph_populate.c | 1 +\n lib/graph/graph_private.h | 44 +++\n lib/graph/graph_stats.c | 74 +++-\n lib/graph/meson.build | 4 +-\n lib/graph/node.c | 1 +\n lib/graph/rte_graph.h | 44 +++\n lib/graph/rte_graph_model_dispatch.c | 179 +++++++++\n lib/graph/rte_graph_model_dispatch.h | 122 ++++++\n lib/graph/rte_graph_model_rtc.h | 45 +++\n lib/graph/rte_graph_worker.c | 54 +++\n lib/graph/rte_graph_worker.h | 498 +------------------------\n lib/graph/rte_graph_worker_common.h | 539 +++++++++++++++++++++++++++\n lib/graph/version.map | 10 +\n 18 files changed, 1553 insertions(+), 544 deletions(-)\n create mode 100644 lib/graph/rte_graph_model_dispatch.c\n create mode 100644 lib/graph/rte_graph_model_dispatch.h\n create mode 100644 lib/graph/rte_graph_model_rtc.h\n create mode 100644 lib/graph/rte_graph_worker.c\n create mode 100644 lib/graph/rte_graph_worker_common.h" }