From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: olivier.matz@6wind.com, jerin.jacob@caviumnetworks.com,
Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-dev] [PATCH v2 0/5] create event rings type
Date: Fri, 30 Jun 2017 16:06:16 +0100 [thread overview]
Message-ID: <20170630150621.156365-1-bruce.richardson@intel.com> (raw)
In-Reply-To: <20170607133620.275801-1-bruce.richardson@intel.com>
Following on from the refactoring of the rte_rings code done in the 17.05
release, it becomes relatively easy to create new ring implementations for
data types other than "void *". The first candidate for this is the
rte_event type, which being 16B in size, is small enough to be passed
around directly rather than via pointer.
The SW eventdev implementation already defines an event ring implementation
and this can be replaced by a more general implementation done in the
eventdev library itself. However, feature parity between the SW eventdev
implementation and a general rte_ring implementation is required, so
support for rings of a defined size is added to the rte_ring library first.
v2: minor adjustments made following review feedback.
Bruce Richardson (5):
ring: allow rings with non power-of-2 sizes
test/test: add unit tests for exact size rings
eventdev: add ring structure for events
test/test: add auto-tests for event ring functions
event/sw: change worker rings to standard event rings
drivers/event/sw/sw_evdev.c | 38 ++--
drivers/event/sw/sw_evdev.h | 4 +-
drivers/event/sw/sw_evdev_scheduler.c | 19 +-
drivers/event/sw/sw_evdev_worker.c | 28 ++-
drivers/event/sw/sw_evdev_xstats.c | 15 +-
lib/Makefile | 2 +-
lib/librte_eventdev/Makefile | 2 +
lib/librte_eventdev/rte_event_ring.c | 207 ++++++++++++++++++
lib/librte_eventdev/rte_event_ring.h | 308 +++++++++++++++++++++++++++
lib/librte_eventdev/rte_eventdev_version.map | 9 +
lib/librte_ring/rte_ring.c | 26 ++-
lib/librte_ring/rte_ring.h | 89 +++++---
test/test/Makefile | 1 +
test/test/test_event_ring.c | 275 ++++++++++++++++++++++++
test/test/test_ring.c | 74 +++++++
15 files changed, 1020 insertions(+), 77 deletions(-)
create mode 100644 lib/librte_eventdev/rte_event_ring.c
create mode 100644 lib/librte_eventdev/rte_event_ring.h
create mode 100644 test/test/test_event_ring.c
--
2.13.0
next prev parent reply other threads:[~2017-06-30 15:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 13:36 [dpdk-dev] [PATCH " Bruce Richardson
2017-06-07 13:36 ` [dpdk-dev] [PATCH 1/5] ring: allow rings with non power-of-2 sizes Bruce Richardson
2017-06-30 9:40 ` Olivier Matz
2017-06-30 11:32 ` Bruce Richardson
2017-06-30 12:24 ` Olivier Matz
2017-06-30 13:59 ` Bruce Richardson
2017-06-07 13:36 ` [dpdk-dev] [PATCH 2/5] test/test: add unit tests for exact size rings Bruce Richardson
2017-06-30 9:42 ` Olivier Matz
2017-06-07 13:36 ` [dpdk-dev] [PATCH 3/5] eventdev: add ring structure for events Bruce Richardson
2017-06-12 5:15 ` Jerin Jacob
2017-06-12 8:53 ` Bruce Richardson
2017-06-30 13:24 ` Bruce Richardson
2017-06-07 13:36 ` [dpdk-dev] [PATCH 4/5] test/test: add auto-tests for event ring functions Bruce Richardson
2017-06-07 13:36 ` [dpdk-dev] [PATCH 5/5] event/sw: change worker rings to standard event rings Bruce Richardson
2017-06-30 15:06 ` Bruce Richardson [this message]
2017-06-30 15:06 ` [dpdk-dev] [PATCH v2 1/5] ring: allow rings with non power-of-2 sizes Bruce Richardson
2017-07-03 8:46 ` Olivier Matz
2017-06-30 15:06 ` [dpdk-dev] [PATCH v2 2/5] test/test: add unit tests for exact size rings Bruce Richardson
2017-07-03 8:47 ` Olivier Matz
2017-06-30 15:06 ` [dpdk-dev] [PATCH v2 3/5] eventdev: add ring structure for events Bruce Richardson
2017-07-03 9:52 ` Van Haaren, Harry
2017-06-30 15:06 ` [dpdk-dev] [PATCH v2 4/5] test/test: add auto-tests for event ring functions Bruce Richardson
2017-07-03 12:30 ` Van Haaren, Harry
2017-06-30 15:06 ` [dpdk-dev] [PATCH v2 5/5] event/sw: change worker rings to standard event rings Bruce Richardson
2017-07-03 12:28 ` Van Haaren, Harry
2017-07-03 12:44 ` Jerin Jacob
2017-07-03 13:01 ` Van Haaren, Harry
2017-07-04 5:36 ` Jerin Jacob
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=20170630150621.156365-1-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=olivier.matz@6wind.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).