From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [RFC PATCH DRAFT 0/2] ethdev: Proposal to expand API for single-pkt-tx
Date: Tue, 24 Jun 2014 23:32:14 +0100 [thread overview]
Message-ID: <1403649136-23551-1-git-send-email-bruce.richardson@intel.com> (raw)
This is an RFC patch to get feedback on this change proposal before I do any
further investigation work into it, looking at all the example apps - as there
are a lot of them. :-)
The idea is to remove all the code in the sample applications for buffering
packets on TX by moving the buffering functionality into the ethdev API, so we
can just do buffered TX of packets, one packet at a time.
For more details, see description in patch 1...
Bruce Richardson (2):
ethdev: add buffered single pkt TX function to API
l2fwd: update l2fwd to use tx_buffer API
config/common_bsdapp | 1 +
config/common_linuxapp | 1 +
examples/l2fwd/main.c | 61 +++++------------------------------------
lib/librte_ether/rte_ethdev.c | 55 +++++++++++++++++++++++++++++++++++--
lib/librte_ether/rte_ethdev.h | 63 +++++++++++++++++++++++++++++++++++++++++++
5 files changed, 125 insertions(+), 56 deletions(-)
--
1.9.3
next reply other threads:[~2014-06-24 22:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 22:32 Bruce Richardson [this message]
2014-06-24 22:32 ` [dpdk-dev] [RFC PATCH DRAFT 1/2] ethdev: add buffered single pkt TX function to API Bruce Richardson
2014-06-24 23:05 ` Stephen Hemminger
2014-06-25 0:05 ` Richardson, Bruce
2014-06-24 23:07 ` Stephen Hemminger
2014-06-25 0:02 ` Richardson, Bruce
2014-06-24 22:32 ` [dpdk-dev] [RFC PATCH DRAFT 2/2] l2fwd: update l2fwd to use tx_buffer API 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=1403649136-23551-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).