From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Jerin Jacob Kollanukkaran" <jerinj@marvell.com>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 00/11] example/l3fwd: introduce event device support
Date: Fri, 27 Sep 2019 07:28:05 +0000 [thread overview]
Message-ID: <CY4PR1801MB1863D0AB0F892371A9FE459EDE810@CY4PR1801MB1863.namprd18.prod.outlook.com> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB977258019196AE77@irsmsx105.ger.corp.intel.com>
Hi Konstantin,
We have actually sent v1 before the cutoff date
http://patches.dpdk.org/patch/58806/.
I missed versioning the patchset as v2.
If it's not feasible to review for current release we could push it to 20.02.
We at least want to push l2fwd-event example for this release.
http://patches.dpdk.org/project/dpdk/list/?series=6498
Pavan.
>-----Original Message-----
>From: Ananyev, Konstantin <konstantin.ananyev@intel.com>
>Sent: Thursday, September 26, 2019 3:41 PM
>To: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>; Jerin
>Jacob Kollanukkaran <jerinj@marvell.com>; akhil.goyal@nxp.com
>Cc: dev@dpdk.org
>Subject: RE: [dpdk-dev] [PATCH 00/11] example/l3fwd: introduce
>event device support
>Hi Pavan,
>
>
>>
>> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>>
>> This patchset adds support for event mode in l3fwd.
>> The poll mode is still the default mode of operation.
>>
>> The following new command line parameters are added:
>> --mode: Dictates the mode of operation either poll or event. If unset
>then
>> 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
>
>>
>> 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.
>>
>> 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
>>
>> 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
>>
>> 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
>>
>> --
>> 2.17.1
next prev parent reply other threads:[~2019-09-27 7:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 10:05 pbhagavatula
2019-09-26 10:05 ` [dpdk-dev] [PATCH 01/11] examples/l3fwd: add framework for event device pbhagavatula
2019-09-26 10:05 ` [dpdk-dev] [PATCH 02/11] examples/l3fwd: split pipelines based on capability pbhagavatula
2019-09-26 10:05 ` [dpdk-dev] [PATCH 03/11] examples/l3fwd: add event device configuration pbhagavatula
2019-09-26 10:05 ` [dpdk-dev] [PATCH 04/11] examples/l3fwd: add ethdev setup based on eventdev pbhagavatula
2019-09-26 10:05 ` [dpdk-dev] [PATCH 05/11] examples/l3fwd: add event port and queue setup pbhagavatula
2019-09-26 10:05 ` [dpdk-dev] [PATCH 06/11] examples/l3fwd: add event eth Rx/Tx adapter setup pbhagavatula
2019-09-26 10:05 ` [dpdk-dev] [PATCH 07/11] examples/l3fwd: add service core setup based on caps pbhagavatula
2019-09-26 10:05 ` [dpdk-dev] [PATCH 08/11] examples/l3fwd: add event lpm main loop pbhagavatula
2019-09-26 10:05 ` [dpdk-dev] [PATCH 09/11] examples/l3fwd: add event em " pbhagavatula
2019-09-27 17:29 ` Stephen Hemminger
2019-09-27 17:30 ` Stephen Hemminger
2019-09-26 10:05 ` [dpdk-dev] [PATCH 10/11] examples/l3fwd: add graceful teardown for eventdevice pbhagavatula
2019-09-26 10:05 ` [dpdk-dev] [PATCH 11/11] doc: update l3fwd user guide to support eventdev pbhagavatula
2019-09-26 10:10 ` [dpdk-dev] [PATCH 00/11] example/l3fwd: introduce event device support Ananyev, Konstantin
2019-09-27 7:28 ` Pavan Nikhilesh Bhagavatula [this message]
2019-09-27 12:59 ` Ananyev, Konstantin
2019-11-15 7:00 ` Thomas Monjalon
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=CY4PR1801MB1863D0AB0F892371A9FE459EDE810@CY4PR1801MB1863.namprd18.prod.outlook.com \
--to=pbhagavatula@marvell.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=konstantin.ananyev@intel.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).