DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maciej Gajdzica <maciejx.t.gajdzica@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/3] port: added ethdev_writer_nodrop and ring_writer_nodrop ports
Date: Mon, 30 Mar 2015 11:56:41 +0200	[thread overview]
Message-ID: <1427709404-28921-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.

Maciej Gajdzica (3):
  port: added WRITER_APPROACH == 1 implementation to ring port
  port: added ethdev_writer_nodrop port
  port: added ring_writer_nodrop port

 lib/librte_port/rte_port_ethdev.c |  230 ++++++++++++++++++++++++++++++
 lib/librte_port/rte_port_ethdev.h |   19 +++
 lib/librte_port/rte_port_ring.c   |  285 +++++++++++++++++++++++++++++++++++++
 lib/librte_port/rte_port_ring.h   |   16 +++
 4 files changed, 550 insertions(+)

-- 
1.7.9.5

             reply	other threads:[~2015-03-30 10:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30  9:56 Maciej Gajdzica [this message]
2015-03-30  9:56 ` [dpdk-dev] [PATCH 1/3] port: added WRITER_APPROACH == 1 implementation to ring port Maciej Gajdzica
2015-03-30 20:50   ` David Marchand
2015-03-30  9:56 ` [dpdk-dev] [PATCH 2/3] port: added ethdev_writer_nodrop port Maciej Gajdzica
2015-03-30 10:22   ` Walukiewicz, Miroslaw
2015-03-30  9:56 ` [dpdk-dev] [PATCH 3/3] port: added ring_writer_nodrop port Maciej Gajdzica
2015-03-30 11:54 ` [dpdk-dev] [PATCH 0/3] port: added ethdev_writer_nodrop and ring_writer_nodrop ports Dumitrescu, Cristian
     [not found] <1430385773-14589-1-git-send-email-maciejx.t.gajdzica@intel.com>
2015-04-30  9:31 ` Gajdzica, MaciejX T

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=1427709404-28921-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 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).