Patch Detail
get:
Show a patch.
patch:
Update a patch.
put:
Update a patch.
GET /api/patches/128265/?format=api
{ "id": 128265, "url": "http://patches.dpdk.org/api/patches/128265/?format=api", "web_url": "http://patches.dpdk.org/project/dpdk/patch/20230607035144.1214492-18-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": "<20230607035144.1214492-18-zhirun.yan@intel.com>", "list_archive_url": "https://inbox.dpdk.org/dev/20230607035144.1214492-18-zhirun.yan@intel.com", "date": "2023-06-07T03:51:44", "name": "[v9,17/17] doc: update multicore dispatch model in graph guides", "commit_ref": null, "pull_url": null, "state": "changes-requested", "archived": true, "hash": "c7c966644f5ab0768416cc98b255dd5ec54f2e75", "submitter": { "id": 1154, "url": "http://patches.dpdk.org/api/people/1154/?format=api", "name": "Yan, Zhirun", "email": "zhirun.yan@intel.com" }, "delegate": { "id": 1, "url": "http://patches.dpdk.org/api/users/1/?format=api", "username": "tmonjalo", "first_name": "Thomas", "last_name": "Monjalon", "email": "thomas@monjalon.net" }, "mbox": "http://patches.dpdk.org/project/dpdk/patch/20230607035144.1214492-18-zhirun.yan@intel.com/mbox/", "series": [ { "id": 28383, "url": "http://patches.dpdk.org/api/series/28383/?format=api", "web_url": "http://patches.dpdk.org/project/dpdk/list/?series=28383", "date": "2023-06-07T03:51:27", "name": "graph enhancement for multi-core dispatch", "version": 9, "mbox": "http://patches.dpdk.org/series/28383/mbox/" } ], "comments": "http://patches.dpdk.org/api/patches/128265/comments/", "check": "success", "checks": "http://patches.dpdk.org/api/patches/128265/checks/", "tags": {}, "related": [], "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 E668342C46;\n\tWed, 7 Jun 2023 06:01:49 +0200 (CEST)", "from mails.dpdk.org (localhost [127.0.0.1])\n\tby mails.dpdk.org (Postfix) with ESMTP id 2D3BD42DB7;\n\tWed, 7 Jun 2023 06:00:43 +0200 (CEST)", "from mga09.intel.com (mga09.intel.com [134.134.136.24])\n by mails.dpdk.org (Postfix) with ESMTP id 48ECF42DA0\n for <dev@dpdk.org>; Wed, 7 Jun 2023 06:00:42 +0200 (CEST)", "from orsmga006.jf.intel.com ([10.7.209.51])\n by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384;\n 06 Jun 2023 21:00:41 -0700", "from dpdk-zhirun-lmm.sh.intel.com ([10.67.119.94])\n by orsmga006.jf.intel.com with ESMTP; 06 Jun 2023 21:00: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=1686110442; x=1717646442;\n h=from:to:cc:subject:date:message-id:in-reply-to:\n references:mime-version:content-transfer-encoding;\n bh=ila3fZHLti86DsooCT/HKV/h1LbGI+Ru4gsKyg3ZXtE=;\n b=AD8s5dxLPbDarQZjmjYCIUaKN+/qVjOILRGYqFsczLf7/fQED0VD+Gwc\n 8Tc6oUl7LX4cRJf0pmr+MQgRzWHGBVzyL4cWp+zH8hxuhYRJu4Kk4QVtt\n 54ruHTCuYNEO4zQh+Gi8Wp6+DvlAaaeJJlOMoy+xlP1gxKF8NbDKgsIOa\n Z0/C4oae3g1CZ6mlK0UHcVLA0NoJFS+oQQnv87zumlCU1scrLt6VbNz/0\n 937u3XqXaJU3Yfmu1ul8aTUaXYTr8zBUBO/5yayx3IGX4WtQky4V/Gj1U\n aCuWF+1V2sfd0PgRRqKseD7EGEwnXkQHqzQzSGVLoPyOJAmbVwXzZsnSj w==;", "X-IronPort-AV": [ "E=McAfee;i=\"6600,9927,10733\"; a=\"359336783\"", "E=Sophos;i=\"6.00,222,1681196400\"; d=\"scan'208\";a=\"359336783\"", "E=McAfee;i=\"6600,9927,10733\"; a=\"686759535\"", "E=Sophos;i=\"6.00,222,1681196400\"; d=\"scan'208\";a=\"686759535\"" ], "X-ExtLoop1": "1", "From": "Zhirun Yan <zhirun.yan@intel.com>", "To": "dev@dpdk.org, jerinj@marvell.com, kirankumark@marvell.com,\n ndabilpuram@marvell.com, stephen@networkplumber.org,\n pbhagavatula@marvell.com, jerinjacobk@gmail.com", "Cc": "cunming.liang@intel.com, haiyue.wang@intel.com,\n mattias.ronnblom@ericsson.com, Zhirun Yan <zhirun.yan@intel.com>", "Subject": "[PATCH v9 17/17] doc: update multicore dispatch model in graph guides", "Date": "Wed, 7 Jun 2023 11:51:44 +0800", "Message-Id": "<20230607035144.1214492-18-zhirun.yan@intel.com>", "X-Mailer": "git-send-email 2.37.2", "In-Reply-To": "<20230607035144.1214492-1-zhirun.yan@intel.com>", "References": "<20230606144746.708388-1-zhirun.yan@intel.com>\n <20230607035144.1214492-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": "Update graph documentation to introduce new multicore dispatch model.\n\nSigned-off-by: Haiyue Wang <haiyue.wang@intel.com>\nSigned-off-by: Cunming Liang <cunming.liang@intel.com>\nSigned-off-by: Zhirun Yan <zhirun.yan@intel.com>\n---\n doc/guides/prog_guide/graph_lib.rst | 68 +++++++++++++++++++++++++++--\n 1 file changed, 64 insertions(+), 4 deletions(-)", "diff": "diff --git a/doc/guides/prog_guide/graph_lib.rst b/doc/guides/prog_guide/graph_lib.rst\nindex 1cfdc86433..8c2c2816ed 100644\n--- a/doc/guides/prog_guide/graph_lib.rst\n+++ b/doc/guides/prog_guide/graph_lib.rst\n@@ -189,14 +189,74 @@ In the above example, A graph object will be created with ethdev Rx\n node of port 0 and queue 0, all ipv4* nodes in the system,\n and ethdev tx node of all ports.\n \n-Multicore graph processing\n-~~~~~~~~~~~~~~~~~~~~~~~~~~\n-In the current graph library implementation, specifically,\n-``rte_graph_walk()`` and ``rte_node_enqueue*`` fast path API functions\n+Graph models chossing\n+~~~~~~~~~~~~~~~~~~~~~\n+Currently, there are 2 different walking models. Use macro\n+RTE_GRAPH_MODEL_SELECT to set the model in compile time. Also offers the\n+ability to choose models in runtime.\n+For application, must #define RTE_GRAPH_MODEL_SELECT before including\n+rte_graph_worker.h.\n+\n+In l3fwd-graph, set RTE_GRAPH_MODEL_SELECT as the model explicitly for\n+performance-sensitive use case.\n+Or set the macro as GRAPH_MODEL_MCORE_RUNTIME_SELECT. And parse\n+``\"--model=NAME\"`` in cmdline and use ``rte_graph_worker_model_set()``\n+to set the walking model in runtime.\n+\n+RTC (Run-To-Completion)\n+^^^^^^^^^^^^^^^^^^^^^^^\n+This is the default graph walking model. Specifically,\n+``rte_graph_walk_rtc()`` and ``rte_node_enqueue*`` fast path API functions\n are designed to work on single-core to have better performance.\n The fast path API works on graph object, So the multi-core graph\n processing strategy would be to create graph object PER WORKER.\n \n+Example:\n+\n+Graph: node-0 -> node-1 -> node-2 @Core0.\n+\n+.. code-block:: diff\n+\n+ + - - - - - - - - - - - - - - - - - - - - - +\n+ ' Core #0 '\n+ ' '\n+ ' +--------+ +---------+ +--------+ '\n+ ' | Node-0 | --> | Node-1 | --> | Node-2 | '\n+ ' +--------+ +---------+ +--------+ '\n+ ' '\n+ + - - - - - - - - - - - - - - - - - - - - - +\n+\n+Dispatch model\n+^^^^^^^^^^^^^^\n+The dispatch model enables a cross-core dispatching mechanism which employs\n+a scheduling work-queue to dispatch streams to other worker cores which\n+being associated with the destination node.\n+\n+Use ``rte_graph_model_mcore_dispatch_lcore_affinity_set()`` to set lcore affinity\n+with the node.\n+Each worker core will have a graph repetition. Use ``rte_graph_clone()`` to clone\n+graph for each worker and use``rte_graph_model_mcore_dispatch_core_bind()`` to\n+bind graph with the worker core.\n+\n+Example:\n+\n+Graph topo: node-0 -> Core1; node-1 -> node-2; node-2 -> node-3.\n+Config 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+\n In fast path\n ~~~~~~~~~~~~\n Typical fast-path code looks like below, where the application\n", "prefixes": [ "v9", "17/17" ] }