From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 9BD24A0613 for ; Thu, 26 Sep 2019 12:10:55 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id EBD3B1BF9A; Thu, 26 Sep 2019 12:10:54 +0200 (CEST) Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 24F6C1BF41 for ; Thu, 26 Sep 2019 12:10:52 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Sep 2019 03:10:52 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,551,1559545200"; d="scan'208";a="364685251" Received: from irsmsx153.ger.corp.intel.com ([163.33.192.75]) by orsmga005.jf.intel.com with ESMTP; 26 Sep 2019 03:10:50 -0700 Received: from irsmsx111.ger.corp.intel.com (10.108.20.4) by IRSMSX153.ger.corp.intel.com (163.33.192.75) with Microsoft SMTP Server (TLS) id 14.3.439.0; Thu, 26 Sep 2019 11:10:49 +0100 Received: from irsmsx105.ger.corp.intel.com ([169.254.7.164]) by irsmsx111.ger.corp.intel.com ([169.254.2.112]) with mapi id 14.03.0439.000; Thu, 26 Sep 2019 11:10:49 +0100 From: "Ananyev, Konstantin" To: "pbhagavatula@marvell.com" , "jerinj@marvell.com" , "akhil.goyal@nxp.com" CC: "dev@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH 00/11] example/l3fwd: introduce event device support Thread-Index: AQHVdFIR4MJvfZSOUUSMX2cQJrtBMqc9vF7A Date: Thu, 26 Sep 2019 10:10:49 +0000 Message-ID: <2601191342CEEE43887BDE71AB977258019196AE77@irsmsx105.ger.corp.intel.com> References: <20190926100558.24348-1-pbhagavatula@marvell.com> In-Reply-To: <20190926100558.24348-1-pbhagavatula@marvell.com> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNWJkMGU3NTctMDgzYS00NmFiLWIyYjctZGVkYzAzNjg2MDE5IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiYk5cL2tlK2FyZklnQTArVkJ2VmtTYTIrVEd0bHFGb1EycXNTTnp2YUxaS2lqQUpcL0IwbHk0UUZhS1ZYSlc0WWZCIn0= x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.2.0.6 dlp-reaction: no-action x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH 00/11] example/l3fwd: introduce event device support X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Pavan, >=20 > From: Pavan Nikhilesh >=20 > This patchset adds support for event mode in l3fwd. > The poll mode is still the default mode of operation. >=20 > The following new command line parameters are added: > --mode: Dictates the mode of operation either poll or event. If unset th= en > by default poll mode is used. > --eventq_sync: Dictates event synchronization mode i.e. either atomic or > ordered. I suppose this patch-set is for 20.02, right? Konstantin >=20 > Based on event device capability the configuration is done as follows: > - A single event device is enabled. > - The number of event ports is equal to the number of worker > cores enabled in the core mask. Additional event ports might > be configured based on Rx/Tx adapter capability. > - The number of event queues is equal to the number of ethernet > ports. If Tx adapter doesn't have internal port capability then > an additional single link event queue is used to enqueue events > to Tx adapter. > - Each event port is linked to all existing event queues. > - Dedicated Rx/Tx adapters for each Ethernet port. >=20 > Pavan Nikhilesh (6): > examples/l3fwd: add event device configuration > examples/l3fwd: add event eth Rx/Tx adapter setup > examples/l3fwd: add service core setup based on caps > examples/l3fwd: add event lpm main loop > examples/l3fwd: add event em main loop > examples/l3fwd: add graceful teardown for eventdevice >=20 > Sunil Kumar Kori (5): > examples/l3fwd: add framework for event device > examples/l3fwd: split pipelines based on capability > examples/l3fwd: add ethdev setup based on eventdev > examples/l3fwd: add event port and queue setup > doc: update l3fwd user guide to support eventdev >=20 > doc/guides/sample_app_ug/l3_forward.rst | 76 +++- > examples/l3fwd/Makefile | 3 +- > examples/l3fwd/l3fwd.h | 38 ++ > examples/l3fwd/l3fwd_em.c | 151 ++++++++ > examples/l3fwd/l3fwd_em.h | 159 +++++--- > examples/l3fwd/l3fwd_em_hlm.h | 131 +++++++ > examples/l3fwd/l3fwd_em_sequential.h | 26 ++ > examples/l3fwd/l3fwd_eventdev.c | 356 ++++++++++++++++++ > examples/l3fwd/l3fwd_eventdev.h | 116 ++++++ > examples/l3fwd/l3fwd_eventdev_generic.c | 222 +++++++++++ > examples/l3fwd/l3fwd_eventdev_internal_port.c | 197 ++++++++++ > examples/l3fwd/l3fwd_lpm.c | 205 ++++++++++ > examples/l3fwd/main.c | 202 ++++++++-- > examples/l3fwd/meson.build | 5 +- > 14 files changed, 1802 insertions(+), 85 deletions(-) > create mode 100644 examples/l3fwd/l3fwd_eventdev.c > create mode 100644 examples/l3fwd/l3fwd_eventdev.h > create mode 100644 examples/l3fwd/l3fwd_eventdev_generic.c > create mode 100644 examples/l3fwd/l3fwd_eventdev_internal_port.c >=20 > -- > 2.17.1