1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
|
.. SPDX-License-Identifier: BSD-3-Clause
Copyright(c) 2018 Ericsson AB
Distributed Software Eventdev Poll Mode Driver
==============================================
The distributed software event device is an eventdev driver which
distributes the task of scheduling events among all the eventdev ports
and the lcore threads using them.
Features
--------
Queues
* Atomic
* Parallel
* Single-Link
Ports
* Load balanced (for Atomic, Ordered, Parallel queues)
* Single Link (for single-link queues)
Configuration and Options
-------------------------
The distributed software eventdev is a vdev device, and as such can be
created from the application code, or from the EAL command line:
* Call ``rte_vdev_init("event_dsw0")`` from the application
* Use ``--vdev="event_dsw0"`` in the EAL options, which will call
rte_vdev_init() internally
Example:
.. code-block:: console
./your_eventdev_application --vdev="event_dsw0"
Limitations
-----------
Unattended Ports
~~~~~~~~~~~~~~~~
The distributed software eventdev uses an internal signaling schema
between the ports to achieve load balancing. In order for this to
work, the application must perform enqueue and/or dequeue operations
on all ports.
Producer-only ports which currently have no events to enqueue should
periodically call rte_event_enqueue_burst() with a zero-sized burst.
Ports left unattended for longer periods of time will prevent load
balancing, and also cause traffic interruptions on the flows which
are in the process of being migrated.
Output Buffering
~~~~~~~~~~~~~~~~
For efficiency reasons, the distributed software eventdev might not
send enqueued events immediately to the destination port, but instead
store them in an internal buffer in the source port.
In case no more events are enqueued on a port with buffered events,
these events will be sent after the application has performed a number
of enqueue and/or dequeue operations.
For explicit flushing, an application may call
rte_event_enqueue_burst() with a zero-sized burst.
Priorities
~~~~~~~~~~
The distributed software eventdev does not support event priorities.
Ordered Queues
~~~~~~~~~~~~~~
The distributed software eventdev does not support the ordered queue type.
"All Types" Queues
~~~~~~~~~~~~~~~~~~
The distributed software eventdev does not support queues of type
RTE_EVENT_QUEUE_CFG_ALL_TYPES, which allow both atomic, ordered, and
parallel events on the same queue.
Dynamic Link/Unlink
~~~~~~~~~~~~~~~~~~~
The distributed software eventdev does not support calls to
rte_event_port_link() or rte_event_port_unlink() after
rte_event_dev_start() has been called.
|
