From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/3] ring: provide rte_ring_as_ethdev API
Date: Fri, 16 May 2014 19:15:11 +0100 [thread overview]
Message-ID: <1400264114-28455-1-git-send-email-bruce.richardson@intel.com> (raw)
This patch set aims to provide a shorter simpler alternative the public API functions for using rings as ethdevs provided by the librte_pmd_ring library. This alternative just provides simple RX and TX burst functions and a conversion API, without any of the complexities present in the pmd_ring version. This replacement should allow the public APIs in the pmd_ring library to be deprecated in the future.
Bruce Richardson (3):
ethdev: Remove ethdev.h dependency on mbuf + mempool
ring: add support for converting a ring to ethdev
ring: autotest for using ring as ethdev
app/test-pmd/cmdline.c | 1 +
app/test/test_pmd_ring.c | 1 +
app/test/test_ring.c | 25 ++++++++++++++++++++
lib/librte_ether/rte_ethdev.h | 4 +++-
lib/librte_pmd_vmxnet3/vmxnet3_ethdev.c | 1 +
lib/librte_ring/Makefile | 1 +
lib/librte_ring/rte_ring.c | 42 +++++++++++++++++++++++++++++++++
lib/librte_ring/rte_ring.h | 11 +++++++++
8 files changed, 85 insertions(+), 1 deletion(-)
--
1.9.0
next reply other threads:[~2014-05-16 18:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 18:15 Bruce Richardson [this message]
2014-05-16 18:15 ` [dpdk-dev] [PATCH 1/3] ethdev: Remove ethdev.h dependency on mbuf + mempool Bruce Richardson
2014-05-16 18:15 ` [dpdk-dev] [PATCH 2/3] ring: add support for converting a ring to ethdev Bruce Richardson
2014-05-16 18:15 ` [dpdk-dev] [PATCH 3/3] ring: autotest for using ring as ethdev Bruce Richardson
2014-05-16 18:54 ` [dpdk-dev] [PATCH 0/3] ring: provide rte_ring_as_ethdev API Neil Horman
2014-05-19 10:59 ` Richardson, Bruce
2014-05-19 13:40 ` Neil Horman
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=1400264114-28455-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).