From: Bruce Richardson <bruce.richardson@intel.com>
To: olivier.matz@6wind.com
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-dev] [PATCH RFCv2 0/4] generalise rte_ring to allow different datatypes
Date: Tue, 24 Jan 2017 10:39:33 +0000 [thread overview]
Message-ID: <1485254377-20098-1-git-send-email-bruce.richardson@intel.com> (raw)
Following on from the previous RFC, this generalises the rte_ring
structure using C constructs rather than using macros. The idea
here is to have the size of the data objects passed in to all common
functions and then switching the code paths, where necessary, based on
those size parameters. For the standard rte_ring APIs, these work on
void pointers, so the extra parameter is always specified as
sizeof(void *). A new event_ring type is also added as a patch to test
out creating and using rings with different size objects.
Comments welcome on this RFC, though I still hope to try out some
other options, as I think there may be still better ways to achieve
the same end.
Bruce Richardson (4):
ring: create common ring files
ring: separate common and rte_ring specific functions
ring: allow common ring to use 8 or 16 byte values
ring: add new event ring class
app/test/Makefile | 1 +
app/test/test_event_ring.c | 83 ++++
lib/librte_ring/Makefile | 8 +-
lib/librte_ring/rte_common_ring.c | 386 ++++++++++++++++
lib/librte_ring/rte_common_ring.h | 925 ++++++++++++++++++++++++++++++++++++++
lib/librte_ring/rte_event_ring.c | 87 ++++
lib/librte_ring/rte_event_ring.h | 696 ++++++++++++++++++++++++++++
lib/librte_ring/rte_ring.c | 320 +------------
lib/librte_ring/rte_ring.h | 606 +------------------------
9 files changed, 2210 insertions(+), 902 deletions(-)
create mode 100644 app/test/test_event_ring.c
create mode 100644 lib/librte_ring/rte_common_ring.c
create mode 100644 lib/librte_ring/rte_common_ring.h
create mode 100644 lib/librte_ring/rte_event_ring.c
create mode 100644 lib/librte_ring/rte_event_ring.h
--
2.9.3
next reply other threads:[~2017-01-24 10:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 10:39 Bruce Richardson [this message]
2017-01-24 10:39 ` [dpdk-dev] [PATCH RFCv2 1/4] ring: create common ring files Bruce Richardson
2017-01-24 10:39 ` [dpdk-dev] [PATCH RFCv2 2/4] ring: separate common and rte_ring specific functions Bruce Richardson
2017-01-24 10:39 ` [dpdk-dev] [PATCH RFCv2 3/4] ring: allow common ring to use 8 or 16 byte values Bruce Richardson
2017-01-24 10:39 ` [dpdk-dev] [PATCH RFCv2 4/4] ring: add new event ring class Bruce Richardson
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=1485254377-20098-1-git-send-email-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--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).