From: Maciej Gajdzica <maciejx.t.gajdzica@intel.com>
To: dev@dpdk.org
Subject: [PATCH v3 0/4] port: add ethdev_writer and ring_writer nodrop ports
Date: Thu, 21 May 2015 14:28:40 +0200 [thread overview]
Message-ID: <1432211324-5078-1-git-send-email-maciejx.t.gajdzica@intel.com> (raw)
When nodrop writer port fails to send data, it retries until reach maximum
number of retries. Also added new tx_bulk implementation for ring writer port.
Changes in v2:
- added missing signoffs
Changes in v3:
- removed second implementation of tx_bulk functions
Maciej Gajdzica (4):
port: removed second implementation of tx_bulk from ethdev_writer
port
port: changed tx_bulk implementation if ring_writer port
port: added ethdev_writer_nodrop port
port: added ring_writer_nodrop port
lib/librte_port/rte_port_ethdev.c | 206 +++++++++++++++++++++++++++++------
lib/librte_port/rte_port_ethdev.h | 19 ++++
lib/librte_port/rte_port_ring.c | 214 +++++++++++++++++++++++++++++++++++--
lib/librte_port/rte_port_ring.h | 16 +++
4 files changed, 409 insertions(+), 46 deletions(-)
--
1.7.9.5
next reply other threads:[~2015-05-21 12:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 12:28 Maciej Gajdzica [this message]
2015-05-21 12:28 ` [PATCH v3 1/4] port: removed second implementation of tx_bulk from ethdev_writer port Maciej Gajdzica
2015-05-21 12:28 ` [PATCH v3 2/4] port: changed tx_bulk implementation if ring_writer port Maciej Gajdzica
2015-05-21 12:28 ` [PATCH v3 3/4] port: added ethdev_writer_nodrop port Maciej Gajdzica
2015-05-21 12:28 ` [PATCH v3 4/4] port: added ring_writer_nodrop port Maciej Gajdzica
2015-05-21 16:30 ` [PATCH v3 0/4] port: add ethdev_writer and ring_writer nodrop ports Dumitrescu, Cristian
2015-06-18 14:42 ` 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=1432211324-5078-1-git-send-email-maciejx.t.gajdzica@intel.com \
--to=maciejx.t.gajdzica@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.