Patch Detail
get:
Show a patch.
patch:
Update a patch.
put:
Update a patch.
GET /api/patches/65068/?format=api
{ "id": 65068, "url": "http://patches.dpdk.org/api/patches/65068/?format=api", "web_url": "http://patches.dpdk.org/project/dpdk/patch/20200122182817.1667-12-pbhagavatula@marvell.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": "<20200122182817.1667-12-pbhagavatula@marvell.com>", "list_archive_url": "https://inbox.dpdk.org/dev/20200122182817.1667-12-pbhagavatula@marvell.com", "date": "2020-01-22T18:28:17", "name": "[v4,11/11] doc: update l3fwd user guide to support eventdev", "commit_ref": null, "pull_url": null, "state": "superseded", "archived": true, "hash": "f86f736820463e2e61280b83772a26365b5c7428", "submitter": { "id": 1183, "url": "http://patches.dpdk.org/api/people/1183/?format=api", "name": "Pavan Nikhilesh Bhagavatula", "email": "pbhagavatula@marvell.com" }, "delegate": { "id": 310, "url": "http://patches.dpdk.org/api/users/310/?format=api", "username": "jerin", "first_name": "Jerin", "last_name": "Jacob", "email": "jerinj@marvell.com" }, "mbox": "http://patches.dpdk.org/project/dpdk/patch/20200122182817.1667-12-pbhagavatula@marvell.com/mbox/", "series": [ { "id": 8269, "url": "http://patches.dpdk.org/api/series/8269/?format=api", "web_url": "http://patches.dpdk.org/project/dpdk/list/?series=8269", "date": "2020-01-22T18:28:06", "name": "example/l3fwd: introduce event device support", "version": 4, "mbox": "http://patches.dpdk.org/series/8269/mbox/" } ], "comments": "http://patches.dpdk.org/api/patches/65068/comments/", "check": "success", "checks": "http://patches.dpdk.org/api/patches/65068/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 dpdk.org (dpdk.org [92.243.14.124])\n\tby inbox.dpdk.org (Postfix) with ESMTP id 21F97A0532;\n\tWed, 22 Jan 2020 19:30:13 +0100 (CET)", "from [92.243.14.124] (localhost [127.0.0.1])\n\tby dpdk.org (Postfix) with ESMTP id 8926D49DF;\n\tWed, 22 Jan 2020 19:29:12 +0100 (CET)", "from mx0b-0016f401.pphosted.com (mx0b-0016f401.pphosted.com\n [67.231.156.173]) by dpdk.org (Postfix) with ESMTP id 169321BE8A\n for <dev@dpdk.org>; Wed, 22 Jan 2020 19:29:10 +0100 (CET)", "from pps.filterd (m0045851.ppops.net [127.0.0.1])\n by mx0b-0016f401.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id\n 00MIKJsq021841; Wed, 22 Jan 2020 10:29:10 -0800", "from sc-exch03.marvell.com ([199.233.58.183])\n by mx0b-0016f401.pphosted.com with ESMTP id 2xm2dt88py-1\n (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT);\n Wed, 22 Jan 2020 10:29:10 -0800", "from SC-EXCH01.marvell.com (10.93.176.81) by SC-EXCH03.marvell.com\n (10.93.176.83) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 22 Jan\n 2020 10:29:07 -0800", "from maili.marvell.com (10.93.176.43) by SC-EXCH01.marvell.com\n (10.93.176.81) with Microsoft SMTP Server id 15.0.1497.2 via Frontend\n Transport; Wed, 22 Jan 2020 10:29:08 -0800", "from BG-LT7430.marvell.com (unknown [10.28.17.83])\n by maili.marvell.com (Postfix) with ESMTP id A5B4E3F7041;\n Wed, 22 Jan 2020 10:29:04 -0800 (PST)" ], "DKIM-Signature": "v=1; a=rsa-sha256; c=relaxed/relaxed; d=marvell.com;\n h=from : to : cc :\n subject : date : message-id : in-reply-to : references : mime-version :\n content-transfer-encoding : content-type; s=pfpt0818;\n bh=LnVd3uLW5Dnzl4rMb70v8LYc2NNc8Df9ZG7yoaWVE98=;\n b=ZWkCbXBWajijKyturu8bXhQyRpOmiksWnE4Ah8zsTuQZeoXpPgPbM+IKclQWyWUeING/\n BVc3T26i3pkqdgcHjthem3Q+amhj0kponrYbLfoEDg0YZd9RLSFGhjY5L8cgkMOai9bN\n DnL+bGTi+C2+2c6j6YDWrbkxvuQIlakCYedvskF26zty3UtaHJk3RZn6tSptrXd1mVOa\n zbuUUz4kzalwtQ+yqCcBG/miQVU7w3OofqhOtZvQQvv/J79ezFw3feUbqp1U3uuePVgP\n 8AKH9agRU71lq5+aiT5hfd+Uy+/eH1ZU3HsBV6V7/iKsF4Lq+q21qDX3ANfrkOmxt5wr Dg==", "From": "<pbhagavatula@marvell.com>", "To": "<jerinj@marvell.com>, <konstantin.ananyev@intel.com>, Marko Kovacevic\n <marko.kovacevic@intel.com>, Ori Kam <orika@mellanox.com>, Bruce Richardson\n <bruce.richardson@intel.com>, Radu Nicolau <radu.nicolau@intel.com>, \"Akhil\n Goyal\" <akhil.goyal@nxp.com>, Tomasz Kantecki <tomasz.kantecki@intel.com>,\n Sunil Kumar Kori <skori@marvell.com>, Pavan Nikhilesh\n <pbhagavatula@marvell.com>, John McNamara <john.mcnamara@intel.com>", "CC": "<dev@dpdk.org>", "Date": "Wed, 22 Jan 2020 23:58:17 +0530", "Message-ID": "<20200122182817.1667-12-pbhagavatula@marvell.com>", "X-Mailer": "git-send-email 2.17.1", "In-Reply-To": "<20200122182817.1667-1-pbhagavatula@marvell.com>", "References": "<20200111134730.5329-1-pbhagavatula@marvell.com>\n <20200122182817.1667-1-pbhagavatula@marvell.com>", "MIME-Version": "1.0", "Content-Transfer-Encoding": "8bit", "Content-Type": "text/plain", "X-Proofpoint-Virus-Version": "vendor=fsecure engine=2.50.10434:6.0.138, 18.0.572\n definitions=2020-01-22_08:2020-01-22,\n 2020-01-22 signatures=0", "Subject": "[dpdk-dev] [PATCH v4 11/11] doc: update l3fwd user guide to support\n\teventdev", "X-BeenThere": "dev@dpdk.org", "X-Mailman-Version": "2.1.15", "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", "Sender": "\"dev\" <dev-bounces@dpdk.org>" }, "content": "From: Pavan Nikhilesh <pbhagavatula@marvell.com>\n\nUpdate l3fwd user guide to include event device related information.\n\nSigned-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>\n---\n doc/guides/sample_app_ug/l3_forward.rst | 79 +++++++++++++++++++++++--\n 1 file changed, 73 insertions(+), 6 deletions(-)", "diff": "diff --git a/doc/guides/sample_app_ug/l3_forward.rst b/doc/guides/sample_app_ug/l3_forward.rst\nindex 4cb4b18da..5cb0abc32 100644\n--- a/doc/guides/sample_app_ug/l3_forward.rst\n+++ b/doc/guides/sample_app_ug/l3_forward.rst\n@@ -4,16 +4,23 @@\n L3 Forwarding Sample Application\n ================================\n \n-The L3 Forwarding application is a simple example of packet processing using the DPDK.\n+The L3 Forwarding application is a simple example of packet processing using\n+DPDK to demonstrate usage of poll and event mode packet I/O mechanism.\n The application performs L3 forwarding.\n \n Overview\n --------\n \n-The application demonstrates the use of the hash and LPM libraries in the DPDK to implement packet forwarding.\n-The initialization and run-time paths are very similar to those of the :doc:`l2_forward_real_virtual`.\n-The main difference from the L2 Forwarding sample application is that the forwarding decision\n-is made based on information read from the input packet.\n+The application demonstrates the use of the hash and LPM libraries in the DPDK\n+to implement packet forwarding using poll or event mode PMDs for packet I/O.\n+The initialization and run-time paths are very similar to those of the\n+:doc:`l2_forward_real_virtual` and :doc:`l2_forward_event`.\n+The main difference from the L2 Forwarding sample application is that optionally\n+packet can be Rx/Tx from/to eventdev instead of port directly and forwarding\n+decision is made based on information read from the input packet.\n+\n+Eventdev can optionally use S/W or H/W (if supported by platform) scheduler\n+implementation for packet I/O based on run time parameters.\n \n The lookup method is either hash-based or LPM-based and is selected at run time. When the selected lookup method is hash-based,\n a hash object is used to emulate the flow classification stage.\n@@ -56,6 +63,9 @@ The application has a number of command line options::\n [--ipv6]\n [--parse-ptype]\n [--per-port-pool]\n+ [--mode]\n+ [--eventq-sched]\n+ [--event-eth-rxqs]\n \n Where,\n \n@@ -86,6 +96,13 @@ Where,\n \n * ``--per-port-pool:`` Optional, set to use independent buffer pools per port. Without this option, single buffer pool is used for all ports.\n \n+* ``--mode:`` Optional, Packet transfer mode for I/O, poll or eventdev.\n+\n+* ``--eventq-sched:`` Optional, Event queue synchronization method, Ordered, Atomic or Parallel. Only valid if --mode=eventdev.\n+\n+* ``--event-eth-rxqs:`` Optionala, Number of ethernet RX queues per device. Only valid if --mode=eventdev.\n+\n+\n For example, consider a dual processor socket platform with 8 physical cores, where cores 0-7 and 16-23 appear on socket 0,\n while cores 8-15 and 24-31 appear on socket 1.\n \n@@ -116,6 +133,51 @@ In this command:\n | | | | |\n +----------+-----------+-----------+-------------------------------------+\n \n+To use eventdev mode with sync method **ordered** on above mentioned environment,\n+Following is the sample command:\n+\n+.. code-block:: console\n+\n+ ./build/l3fwd -l 0-3 -n 4 -w <event device> -- -p 0x3 --eventq-sched=ordered\n+\n+or\n+\n+.. code-block:: console\n+\n+ ./build/l3fwd -l 0-3 -n 4 -w <event device> -- -p 0x03 --mode=eventdev --eventq-sched=ordered\n+\n+In this command:\n+\n+* -w option whitelist the event device supported by platform. Way to pass this device may vary based on platform.\n+\n+* The --mode option defines PMD to be used for packet I/O.\n+\n+* The --eventq-sched option enables synchronization menthod of event queue so that packets will be scheduled accordingly.\n+\n+If application uses S/W scheduler, it uses following DPDK services:\n+\n+* Software scheduler\n+* Rx adapter service function\n+* Tx adapter service function\n+\n+Application needs service cores to run above mentioned services. Service cores\n+must be provided as EAL parameters along with the --vdev=event_sw0 to enable S/W\n+scheduler. Following is the sample command:\n+\n+.. code-block:: console\n+\n+ ./build/l3fwd -l 0-7 -s 0-3 -n 4 --vdev event_sw0 -- -p 0x3 --mode=eventdev --eventq-sched=ordered\n+\n+In case of eventdev mode, *--config* option is not used for ethernet port\n+configuration. Instead each ethernet port will be configured with mentioned\n+setup:\n+\n+* Single Rx/Tx queue\n+\n+* Each Rx queue will be connected to event queue via Rx adapter.\n+\n+* Each Tx queue will be connected via Tx adapter.\n+\n Refer to the *DPDK Getting Started Guide* for general information on running applications and\n the Environment Abstraction Layer (EAL) options.\n \n@@ -125,7 +187,7 @@ Explanation\n -----------\n \n The following sections provide some explanation of the sample application code. As mentioned in the overview section,\n-the initialization and run-time paths are very similar to those of the :doc:`l2_forward_real_virtual`.\n+the initialization and run-time paths are very similar to those of the :doc:`l2_forward_real_virtual` and :doc:`l2_forward_event`.\n The following sections describe aspects that are specific to the L3 Forwarding sample application.\n \n Hash Initialization\n@@ -315,3 +377,8 @@ for LPM-based lookups is done by the get_ipv4_dst_port() function below:\n \n return ((rte_lpm_lookup(ipv4_l3fwd_lookup_struct, rte_be_to_cpu_32(ipv4_hdr->dst_addr), &next_hop) == 0)? next_hop : portid);\n }\n+\n+Eventdev Driver Initialization\n+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n+Eventdev driver initialization is same as L2 forwarding eventdev application.\n+Refer :doc:`l2_forward_event` for more details.\n", "prefixes": [ "v4", "11/11" ] }