[dpdk-dev] [PATCH v2 7/7] doc: update software event device
Pavan Nikhilesh
pbhagavatula at caviumnetworks.com
Fri Oct 13 18:36:50 CEST 2017
From: Pavan Bhagavatula <pbhagavatula at caviumnetworks.com>
Update software event device documentation to include use of service
cores for event distribution.
Signed-off-by: Pavan Nikhilesh <pbhagavatula at caviumnetworks.com>
Acked-by: John McNamara <john.mcnamara at intel.com>
---
doc/guides/eventdevs/sw.rst | 13 ++++++-------
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/doc/guides/eventdevs/sw.rst b/doc/guides/eventdevs/sw.rst
index a3e6624..ec49b3b 100644
--- a/doc/guides/eventdevs/sw.rst
+++ b/doc/guides/eventdevs/sw.rst
@@ -78,9 +78,9 @@ Scheduling Quanta
~~~~~~~~~~~~~~~~~
The scheduling quanta sets the number of events that the device attempts to
-schedule before returning to the application from the ``rte_event_schedule()``
-function. Note that is a *hint* only, and that fewer or more events may be
-scheduled in a given iteration.
+schedule in a single schedule call performed by the service core. Note that
+is a *hint* only, and that fewer or more events may be scheduled in a given
+iteration.
The scheduling quanta can be set using a string argument to the vdev
create call:
@@ -140,10 +140,9 @@ eventdev.
Distributed Scheduler
~~~~~~~~~~~~~~~~~~~~~
-The software eventdev is a centralized scheduler, requiring the
-``rte_event_schedule()`` function to be called by a CPU core to perform the
-required event distribution. This is not really a limitation but rather a
-design decision.
+The software eventdev is a centralized scheduler, requiring a service core to
+perform the required event distribution. This is not really a limitation but
+rather a design decision.
The ``RTE_EVENT_DEV_CAP_DISTRIBUTED_SCHED`` flag is not set in the
``event_dev_cap`` field of the ``rte_event_dev_info`` struct for the software
--
2.7.4
More information about the dev
mailing list