From c86ced193a541b081421fef66ebe106ad86e355e Mon Sep 17 00:00:00 2001 From: Pavan Nikhilesh Date: Wed, 25 Oct 2017 19:51:44 +0530 Subject: [PATCH] doc: update eventdev guide Update the guide with event queue configuration and event enqueue operation. Signed-off-by: Pavan Nikhilesh Acked-by: Harry van Haaren --- doc/guides/prog_guide/eventdev.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/guides/prog_guide/eventdev.rst b/doc/guides/prog_guide/eventdev.rst index 908d123a68..be9fccddcb 100644 --- a/doc/guides/prog_guide/eventdev.rst +++ b/doc/guides/prog_guide/eventdev.rst @@ -217,7 +217,7 @@ calling the setup function. Repeat this step for each queue, starting from .. code-block:: c struct rte_event_queue_conf atomic_conf = { - .event_queue_cfg = RTE_EVENT_QUEUE_CFG_ATOMIC_ONLY, + .schedule_type = RTE_SCHED_TYPE_ATOMIC, .priority = RTE_EVENT_DEV_PRIORITY_NORMAL, .nb_atomic_flows = 1024, .nb_atomic_order_sequences = 1024, @@ -320,7 +320,7 @@ The following code shows how those packets can be enqueued into the eventdev: for (i = 0; i < nb_rx; i++) { ev[i].flow_id = mbufs[i]->hash.rss; ev[i].op = RTE_EVENT_OP_NEW; - ev[i].sched_type = RTE_EVENT_QUEUE_CFG_ATOMIC_ONLY; + ev[i].sched_type = RTE_SCHED_TYPE_ATOMIC; ev[i].queue_id = 0; ev[i].event_type = RTE_EVENT_TYPE_ETHDEV; ev[i].sub_event_type = 0;