From: Pavan Nikhilesh Date: Wed, 25 Oct 2017 14:50:33 +0000 (+0530) Subject: doc: update software event device X-Git-Tag: spdx-start~1040 X-Git-Url: http://git.droids-corp.org/?a=commitdiff_plain;h=12a33b67dd814ab1f497e51bf3069d0482b8e069;p=dpdk.git doc: update software event device Update software event device documentation to include use of service cores for event distribution. Signed-off-by: Pavan Nikhilesh Acked-by: John McNamara --- diff --git a/doc/guides/eventdevs/sw.rst b/doc/guides/eventdevs/sw.rst index a3e66243e6..ec49b3b577 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 diff --git a/doc/guides/tools/testeventdev.rst b/doc/guides/tools/testeventdev.rst index 34b1c31835..5aa2237b5c 100644 --- a/doc/guides/tools/testeventdev.rst +++ b/doc/guides/tools/testeventdev.rst @@ -106,10 +106,6 @@ The following are the application command-line options: Set the number of mbufs to be allocated from the mempool. -* ``--slcore `` - - Set the scheduler lcore id.(Valid when eventdev is not RTE_EVENT_DEV_CAP_DISTRIBUTED_SCHED capable) - * ``--plcores `` Set the list of cores to be used as producers. @@ -362,7 +358,6 @@ Supported application command line options are following:: --test --socket_id --pool_sz - --slcore (Valid when eventdev is not RTE_EVENT_DEV_CAP_DISTRIBUTED_SCHED capable) --plcores --wlcores --stlist @@ -379,8 +374,8 @@ Example command to run perf queue test: .. code-block:: console - sudo build/app/dpdk-test-eventdev --vdev=event_sw0 -- \ - --test=perf_queue --slcore=1 --plcores=2 --wlcore=3 --stlist=p --nb_pkts=0 + sudo build/app/dpdk-test-eventdev -c 0xf -s 0x1 --vdev=event_sw0 -- \ + --test=perf_queue --plcores=2 --wlcore=3 --stlist=p --nb_pkts=0 PERF_ATQ Test @@ -441,7 +436,6 @@ Supported application command line options are following:: --test --socket_id --pool_sz - --slcore (Valid when eventdev is not RTE_EVENT_DEV_CAP_DISTRIBUTED_SCHED capable) --plcores --wlcores --stlist