From: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
To: jerin.jacob@caviumnetworks.com, harry.van.haaren@intel.com,
hemant.agrawal@nxp.com, santosh.shukla@caviumnetworks.com
Cc: dev@dpdk.org, Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Subject: [PATCH 0/7] eventdev: remove event schedule API for SW driver
Date: Wed, 11 Oct 2017 14:39:43 +0530 [thread overview]
Message-ID: <1507712990-13064-1-git-send-email-pbhagavatula@caviumnetworks.com> (raw)
The software event dev is a centralized software scheduler and needs
`rte_event_schedule` to be called repeatedly in order to distribute the
events. In most cases, this requires a dedicated lcore to achieve this.
With the introduction to the rte_service concept, software eventdev
driver can register event distribution as a service component and
offload it to a service core. Thus removing the requirement of calling
`rte_event_schedule` explicitly and abstracts the differences between
HW and SW PMD to provide a single interface to the application.
Pavan Nikhilesh (7):
eventdev: add API to get service id
event/sw: extend service capability
app/test-eventdev: update app to use service cores
test/eventdev: update test to use service core
examples/eventdev: update sample app to use service
eventdev: remove eventdev schedule API
doc: update software event device
app/test-eventdev/evt_common.h | 41 ++++++++++
app/test-eventdev/evt_options.c | 10 ---
app/test-eventdev/test_order_atq.c | 6 ++
app/test-eventdev/test_order_common.c | 3 -
app/test-eventdev/test_order_queue.c | 6 ++
app/test-eventdev/test_perf_atq.c | 6 ++
app/test-eventdev/test_perf_common.c | 21 -----
app/test-eventdev/test_perf_common.h | 1 +
app/test-eventdev/test_perf_queue.c | 6 ++
doc/guides/eventdevs/sw.rst | 13 ++--
drivers/event/octeontx/ssovf_evdev.c | 1 -
drivers/event/skeleton/skeleton_eventdev.c | 2 -
drivers/event/sw/sw_evdev.c | 10 ++-
examples/eventdev_pipeline_sw_pmd/main.c | 51 +++++++-----
lib/librte_eventdev/rte_eventdev.c | 17 ++++
lib/librte_eventdev/rte_eventdev.h | 53 +++++++------
test/test/test_eventdev_sw.c | 120 ++++++++++++++++-------------
17 files changed, 223 insertions(+), 144 deletions(-)
--
2.7.4
next reply other threads:[~2017-10-11 9:10 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 9:09 Pavan Nikhilesh [this message]
2017-10-11 9:09 ` [PATCH 1/7] eventdev: add API to get service id Pavan Nikhilesh
2017-10-11 9:09 ` [PATCH 2/7] event/sw: extend service capability Pavan Nikhilesh
2017-10-11 9:09 ` [PATCH 3/7] app/test-eventdev: update app to use service cores Pavan Nikhilesh
2017-10-11 9:09 ` [PATCH 4/7] test/eventdev: update test to use service core Pavan Nikhilesh
2017-10-11 9:09 ` [PATCH 5/7] examples/eventdev: update sample app to use service Pavan Nikhilesh
2017-10-11 9:09 ` [PATCH 6/7] eventdev: remove eventdev schedule API Pavan Nikhilesh
2017-10-11 9:09 ` [PATCH 7/7] doc: update software event device Pavan Nikhilesh
2017-10-12 12:29 ` Mcnamara, John
2017-10-13 16:36 ` [PATCH v2 1/7] eventdev: add API to get service id Pavan Nikhilesh
2017-10-13 16:36 ` [PATCH v2 2/7] event/sw: extend service capability Pavan Nikhilesh
2017-10-20 10:30 ` Van Haaren, Harry
2017-10-13 16:36 ` [PATCH v2 3/7] app/test-eventdev: update app to use service cores Pavan Nikhilesh
2017-10-21 17:01 ` Jerin Jacob
2017-10-13 16:36 ` [PATCH v2 4/7] test/eventdev: update test to use service core Pavan Nikhilesh
2017-10-13 16:36 ` [PATCH v2 5/7] examples/eventdev: update sample app to use service Pavan Nikhilesh
2017-10-23 17:17 ` Van Haaren, Harry
2017-10-23 17:51 ` Pavan Nikhilesh Bhagavatula
2017-10-13 16:36 ` [PATCH v2 6/7] eventdev: remove eventdev schedule API Pavan Nikhilesh
2017-10-21 17:07 ` Jerin Jacob
2017-10-13 16:36 ` [PATCH v2 7/7] doc: update software event device Pavan Nikhilesh
2017-10-20 10:21 ` [PATCH v2 1/7] eventdev: add API to get service id Van Haaren, Harry
2017-10-20 11:11 ` Pavan Nikhilesh Bhagavatula
2017-10-22 9:16 ` [PATCH v3 " Pavan Nikhilesh
2017-10-22 9:16 ` [PATCH v3 2/7] event/sw: extend service capability Pavan Nikhilesh
2017-10-22 9:16 ` [PATCH v3 3/7] app/test-eventdev: update app to use service cores Pavan Nikhilesh
2017-10-22 9:16 ` [PATCH v3 4/7] test/eventdev: update test to use service core Pavan Nikhilesh
2017-10-22 9:16 ` [PATCH v3 5/7] examples/eventdev: update sample app to use service Pavan Nikhilesh
2017-10-22 9:16 ` [PATCH v3 6/7] eventdev: remove eventdev schedule API Pavan Nikhilesh
2017-10-22 9:16 ` [PATCH v3 7/7] doc: update software event device Pavan Nikhilesh
2017-10-25 11:59 ` [PATCH v4 1/7] eventdev: add API to get service id Pavan Nikhilesh
2017-10-25 11:59 ` [PATCH v4 2/7] event/sw: extend service capability Pavan Nikhilesh
2017-10-25 11:59 ` [PATCH v4 3/7] app/test-eventdev: update app to use service cores Pavan Nikhilesh
2017-10-25 11:59 ` [PATCH v4 4/7] test/eventdev: update test to use service iter Pavan Nikhilesh
2017-10-25 14:24 ` Van Haaren, Harry
2017-10-25 11:59 ` [PATCH v4 5/7] examples/eventdev: update sample app to use service Pavan Nikhilesh
2017-10-25 14:24 ` Van Haaren, Harry
2017-10-25 11:59 ` [PATCH v4 6/7] eventdev: remove eventdev schedule API Pavan Nikhilesh
2017-10-25 11:59 ` [PATCH v4 7/7] doc: update software event device Pavan Nikhilesh
2017-10-25 14:50 ` [PATCH v5 1/7] eventdev: add API to get service id Pavan Nikhilesh
2017-10-25 14:50 ` [PATCH v5 2/7] event/sw: extend service capability Pavan Nikhilesh
2017-10-25 14:50 ` [PATCH v5 3/7] app/test-eventdev: update app to use service cores Pavan Nikhilesh
2017-10-25 14:50 ` [PATCH v5 4/7] test/eventdev: update test to use service iter Pavan Nikhilesh
2017-10-25 14:50 ` [PATCH v5 5/7] examples/eventdev: update sample app to use service Pavan Nikhilesh
2017-10-25 14:50 ` [PATCH v5 6/7] eventdev: remove eventdev schedule API Pavan Nikhilesh
2017-10-25 14:50 ` [PATCH v5 7/7] doc: update software event device Pavan Nikhilesh
2017-10-26 22:47 ` [PATCH v5 1/7] eventdev: add API to get service id Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1507712990-13064-1-git-send-email-pbhagavatula@caviumnetworks.com \
--to=pbhagavatula@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=santosh.shukla@caviumnetworks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.