From: Tomasz Kulasek <tomaszx.kulasek@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/2] add support for buffered tx to ethdev
Date: 15 Jan 2016 06:26:02 -0800 [thread overview]
Message-ID: <2fd2ae$qhrqne@orsmga002.jf.intel.com> (raw)
Date: Fri, 15 Jan 2016 15:25:30 +0100
Message-Id: <1452867932-5548-1-git-send-email-tomaszx.kulasek@intel.com>
X-Mailer: git-send-email 2.1.4
Many sample apps include internal buffering for single-packet-at-a-time
operation. Since this is such a common paradigm, this functionality is
better suited to being inside the core ethdev API.
The new APIs in the ethdev library are:
* rte_eth_tx_buffer - buffer up a single packet for future transmission
* rte_eth_tx_buffer_flush - flush any unsent buffered packets
* rte_eth_tx_buffer_set_err_callback - set up a callback to be called in
case transmitting a buffered burst fails. By default, we just free the
unsent packets.
As well as these, an additional reference callback is provided, which
frees the packets (as the default callback does), as well as updating a
user-provided counter, so that the number of dropped packets can be
tracked.
The internal buffering of packets for TX in sample apps is no longer
needed, so this patchset also replaces this code with calls to the new
rte_eth_tx_buffer* APIs in:
* l2fwd-jobstats
* l2fwd-keepalive
* l2fwd
* l3fwd-acl
* l3fwd-power
* link_status_interrupt
* client_server_mp
* l2fwd_fork
* packet_ordering
* qos_meter
Tomasz Kulasek (2):
ethdev: add buffered tx api
examples: sample apps rework to use buffered tx api
config/common_bsdapp | 1 +
config/common_linuxapp | 1 +
examples/l2fwd-jobstats/main.c | 73 ++-----
examples/l2fwd-keepalive/main.c | 79 ++------
examples/l2fwd/main.c | 80 ++------
examples/l3fwd-acl/main.c | 64 +-----
examples/l3fwd-power/main.c | 63 +-----
examples/link_status_interrupt/main.c | 83 ++------
.../client_server_mp/mp_client/client.c | 77 +++----
examples/multi_process/l2fwd_fork/main.c | 81 ++------
examples/packet_ordering/main.c | 62 +++---
examples/qos_meter/main.c | 46 +----
lib/librte_ether/rte_ethdev.c | 63 +++++-
lib/librte_ether/rte_ethdev.h | 211 +++++++++++++++++++-
lib/librte_ether/rte_ether_version.map | 8 +
15 files changed, 445 insertions(+), 547 deletions(-)
--
1.7.9.5
next reply other threads:[~2016-01-15 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 14:26 Tomasz Kulasek [this message]
2016-01-15 14:58 ` Kulasek, TomaszX
2016-01-15 14:43 Tomasz Kulasek
2016-01-15 18:12 ` Stephen Hemminger
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='2fd2ae$qhrqne@orsmga002.jf.intel.com' \
--to=tomaszx.kulasek@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).