From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/4] eth_ring: perf test and usability improvements
Date: Wed, 30 Sep 2015 13:12:18 +0100 [thread overview]
Message-ID: <1443615142-24381-1-git-send-email-bruce.richardson@intel.com> (raw)
This patchset makes it easier to create ring pmd instances from code, by
providing a simple ring->ethdev wrapper function and also ensuring that
any created rings are ready for use immediately, without having to call
configure and rx/tx queue setup.
This set also contains a set of unit tests to compare the performance of
basic ring operations against the same operations via the ring ethdev.
This shows how the perf penalty can be significant for small bursts, but
is much less so for larger bursts of 32 packets.
Bruce Richardson (4):
ring: enhance rte_eth_from_rings
rte_ring: store memzone pointer inside ring
ring: add rte_eth_from_ring function
test: Add perf test for ring pmd
app/test/Makefile | 1 +
app/test/test_pmd_ring_perf.c | 188 ++++++++++++++++++++++++++++++
drivers/net/ring/rte_eth_ring.c | 55 ++++++++-
drivers/net/ring/rte_eth_ring.h | 14 +++
drivers/net/ring/rte_eth_ring_version.map | 5 +
lib/librte_ring/rte_ring.c | 1 +
lib/librte_ring/rte_ring.h | 4 +
7 files changed, 262 insertions(+), 6 deletions(-)
create mode 100644 app/test/test_pmd_ring_perf.c
--
2.4.3
next reply other threads:[~2015-09-30 12:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 12:12 Bruce Richardson [this message]
2015-09-30 12:12 ` [dpdk-dev] [PATCH 1/4] ring: enhance rte_eth_from_rings Bruce Richardson
2015-09-30 12:12 ` [dpdk-dev] [PATCH 2/4] rte_ring: store memzone pointer inside ring Bruce Richardson
2015-10-13 14:29 ` Olivier MATZ
2015-09-30 12:12 ` [dpdk-dev] [PATCH 3/4] ring: add rte_eth_from_ring function Bruce Richardson
2015-09-30 12:12 ` [dpdk-dev] [PATCH 4/4] test: Add perf test for ring pmd Bruce Richardson
2015-10-30 13:53 ` [dpdk-dev] [PATCH 0/4] eth_ring: perf test and usability improvements De Lara Guarch, Pablo
2015-11-03 1:02 ` 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=1443615142-24381-1-git-send-email-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
/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).