Lines Matching refs:eventdev

13 The eventdev framework introduces the event driven programming model. In a
27 Step-by-step instructions of the eventdev design is available in the `API
33 The eventdev API represents each event with a generic struct, which contains a
34 payload and metadata required for scheduling by an eventdev.  The
49   eventdev about the status of the event - valid values are NEW, FORWARD or
92 events to the eventdev. An example of a PMD of this type is the eventdev
122 Ports are the points of contact between worker cores and the eventdev. The
124 events from an eventdev. Ports are linked to queues in order to retrieve events
131 This section will introduce the reader to the eventdev API, showing how to
132 create and configure an eventdev and use it for a two-stage atomic pipeline
142    Sample eventdev usage, with RX, two atomic stages and a single-link to TX.
157 The eventdev library uses vdev options to add devices to the DPDK application.
158 The ``--vdev`` EAL option allows adding eventdev instances to your DPDK
159 application, using the name of the eventdev PMD as an argument.
161 For example, to create an instance of the software eventdev scheduler, the
168 In the following code, we configure eventdev instance with 3 queues
189 Once the eventdev itself is configured, the next step is to configure queues.
267 eventdev is capable of scheduling events, and when cores request work to do,
269 from e.g.: a NIC so it is not linked to any eventdev queues.
291 A single function call tells the eventdev instance to start processing
295 eventdev.
309 Now that the eventdev is set up, and ready to receive events, the RX core must
312 The following code shows how those packets can be enqueued into the eventdev:
341 eventdev.
368 to inform the eventdev that the packet is no longer being handled by the
387 The eventdev library allows an application to easily schedule events as it
389 queues and ports abstract the logical functionality of an eventdev, providing