From: Liang Ma <liang.j.ma@intel.com>
To: jerin.jacob@caviumnetworks.com
Cc: dev@dpdk.org, harry.van.haaren@intel.com,
bruce.richardson@intel.com, deepak.k.jain@intel.com,
john.geary@intel.com, peter.mccarthy@intel.com, seanbh@gmail.com
Subject: [dpdk-dev] [RFC v2 PATCH 0/8] event: eventdev OPDL PMD
Date: Fri, 15 Dec 2017 11:26:21 +0000 [thread overview]
Message-ID: <1513337189-137661-1-git-send-email-liang.j.ma@intel.com> (raw)
The OPDL (Ordered Packet Distribution Library) eventdev is a specific
implementation of the eventdev API. It is particularly suited to packet
processing workloads that have high throughput and low latency
requirements. All packets follow the same path through the device.
The order which packets follow is determinted by the order in which
queues are set up. Packets are left on the ring until they are transmitted.
As a result packets do not go out of order.
Features:
The OPDL eventdev implements a subset of features of the eventdev API;
Queues
* Atomic
* Ordered (Parallel is supported as parallel is a subset of Ordered)
* Single-Link
Ports
* Load balanced (for Atomic, Ordered, Parallel queues)
* Single Link (for single-link queues)
Single Port Queue
It is possible to create a Single Port Queue
RTE_EVENT_QUEUE_CFG_SINGLE_LINK. Packets dequeued from this queue do
not need to be re-enqueued (as is the case with an ordered queue). The
purpose of this queue is to allow for asynchronous handling of packets in
the middle of a pipeline. Ordered queues in the middle of a pipeline
cannot delete packets.
Queue Dependencies
As stated the order in which packets travel through queues is static in
nature. They go through the queues in the order the queues are setup at
initialisation rte_event_queue_setup(). For example if an application
sets up 3 queues, Q0, Q1, Q2 and has 3 assoicated ports P0, P1, P2 and
P3 then packets must be
* Enqueued onto Q0 (typically through P0), then
* Dequeued from Q0 (typically through P1), then
* Enqueued onto Q1 (also through P1), then
* Dequeued from Q2 (typically through P2), then
* Enqueued onto Q3 (also through P2), then
* Dequeued from Q3 (typically through P3) and then transmitted on the
relevant eth port
Limitations
The opdl implementation has a number of limitations. These limitations are
due to the static nature of the underlying queues. It is because of this
that the implementation can achieve such high throughput and low latency
The following list is a comprehensive outline of the what is supported and
the limitations / restrictions imposed by the opdl pmd
- The order in which packets moved between queues is static and fixed
(dynamic scheduling is not supported).
- NEW, RELEASE op type are not explicitly supported. RX (first enqueue)
implicitly adds NEW event types, and TX (last dequeue) implicitly does
RELEASE event types.
- All packets follow the same path through device queues.
- Flows within queues are NOT supported.
- Event priority is NOT supported.
- Once the device is stopped all inflight events are lost. Applications should
clear all inflight events before stopping it.
- Each port can only be associated with one queue.
- Each queue can have multiple ports associated with it.
- Each worker core has to dequeue the maximum burst size for that port.
Reference
General concept of event driven programming model
[http://dpdk.org/doc/guides/eventdevs/index.html]
Original Ordered Pipeline Design slides
[https://dpdksummit.com/Archive/pdf/2017Asia/DPDK-China2017-Ma-OPDL.pdf]
Liang Ma (8):
event/opdl: add the opdl ring infrastructure library
event/opdl: add the opdl pmd header and init helper function
event/opdl: add the opdl pmd main body and xstats helper function
eventdev/opdl: opdl eventdev pmd unit test function
lib/librte_eventdev: extend the eventdev capability flags
event/*: apply the three new capability flags for sw/dppa2/octeontx
event/opdl: update the build system to enable compilation
doc: add eventdev opdl pmd docuement
config/common_base | 6 +
doc/guides/eventdevs/index.rst | 1 +
doc/guides/eventdevs/opdl.rst | 162 +++
drivers/event/Makefile | 1 +
drivers/event/dpaa2/dpaa2_eventdev.c | 5 +-
drivers/event/octeontx/ssovf_evdev.c | 5 +-
drivers/event/opdl/Makefile | 66 ++
drivers/event/opdl/opdl_evdev.c | 744 +++++++++++++
drivers/event/opdl/opdl_evdev.h | 354 ++++++
drivers/event/opdl/opdl_evdev_init.c | 951 ++++++++++++++++
drivers/event/opdl/opdl_evdev_xstats.c | 205 ++++
drivers/event/opdl/opdl_ring.c | 1232 +++++++++++++++++++++
drivers/event/opdl/opdl_ring.h | 601 ++++++++++
drivers/event/opdl/opdl_test.c | 1079 ++++++++++++++++++
drivers/event/opdl/rte_pmd_evdev_opdl_version.map | 3 +
drivers/event/sw/sw_evdev.c | 5 +-
lib/librte_eventdev/rte_eventdev.h | 22 +
mk/rte.app.mk | 1 +
18 files changed, 5440 insertions(+), 3 deletions(-)
create mode 100644 doc/guides/eventdevs/opdl.rst
create mode 100644 drivers/event/opdl/Makefile
create mode 100644 drivers/event/opdl/opdl_evdev.c
create mode 100644 drivers/event/opdl/opdl_evdev.h
create mode 100644 drivers/event/opdl/opdl_evdev_init.c
create mode 100644 drivers/event/opdl/opdl_evdev_xstats.c
create mode 100644 drivers/event/opdl/opdl_ring.c
create mode 100644 drivers/event/opdl/opdl_ring.h
create mode 100644 drivers/event/opdl/opdl_test.c
create mode 100644 drivers/event/opdl/rte_pmd_evdev_opdl_version.map
--
2.7.5
--------------------------------------------------------------
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.
next reply other threads:[~2017-12-15 11:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 11:26 Liang Ma [this message]
2017-12-15 11:26 ` [dpdk-dev] [PATCH v2 1/8] event/opdl: add the opdl ring infrastructure library Liang Ma
2017-12-15 12:38 ` Neil Horman
2017-12-15 13:50 ` Ma, Liang
2017-12-15 21:23 ` Neil Horman
2017-12-18 11:05 ` Ma, Liang
2017-12-16 10:14 ` Jerin Jacob
2017-12-15 11:26 ` [dpdk-dev] [PATCH v2 2/8] event/opdl: add the opdl pmd header and init helper function Liang Ma
2017-12-15 11:26 ` [dpdk-dev] [PATCH v2 3/8] event/opdl: add the opdl pmd main body and xstats " Liang Ma
2017-12-16 12:09 ` Jerin Jacob
2017-12-15 11:26 ` [dpdk-dev] [PATCH v2 4/8] eventdev/opdl: opdl eventdev pmd unit test function Liang Ma
2017-12-16 12:12 ` Jerin Jacob
2017-12-15 11:26 ` [dpdk-dev] [PATCH v2 5/8] lib/librte_eventdev: extend the eventdev capability flags Liang Ma
2017-12-15 11:26 ` [dpdk-dev] [PATCH v2 6/8] event/*: apply the three new capability flags for sw/dppa2/octeontx Liang Ma
2017-12-15 11:26 ` [dpdk-dev] [PATCH v2 7/8] event/opdl: update the build system to enable compilation Liang Ma
2017-12-16 12:15 ` Jerin Jacob
2017-12-15 11:26 ` [dpdk-dev] [PATCH v2 8/8] doc: add eventdev opdl pmd docuement Liang Ma
2017-12-15 11:50 ` [dpdk-dev] [RFC v2 PATCH 0/8] event: eventdev OPDL PMD Ma, Liang
2017-12-18 9:12 ` Jerin Jacob
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=1513337189-137661-1-git-send-email-liang.j.ma@intel.com \
--to=liang.j.ma@intel.com \
--cc=bruce.richardson@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=john.geary@intel.com \
--cc=peter.mccarthy@intel.com \
--cc=seanbh@gmail.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).