DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Gajdzica, MaciejX T" <maciejx.t.gajdzica@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 0/4] port: add ethdev_writer and ring_writer	nodrop ports
Date: Thu, 18 Jun 2015 16:42:17 +0200	[thread overview]
Message-ID: <1455064.PMMjulFsjS@xps13> (raw)
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D891263236B051@IRSMSX108.ger.corp.intel.com>

> > 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
> 
> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>

Applied, thanks

      reply	other threads:[~2015-06-18 14:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21 12:28 Maciej Gajdzica
2015-05-21 12:28 ` [dpdk-dev] [PATCH v3 1/4] port: removed second implementation of tx_bulk from ethdev_writer port Maciej Gajdzica
2015-05-21 12:28 ` [dpdk-dev] [PATCH v3 2/4] port: changed tx_bulk implementation if ring_writer port Maciej Gajdzica
2015-05-21 12:28 ` [dpdk-dev] [PATCH v3 3/4] port: added ethdev_writer_nodrop port Maciej Gajdzica
2015-05-21 12:28 ` [dpdk-dev] [PATCH v3 4/4] port: added ring_writer_nodrop port Maciej Gajdzica
2015-05-21 16:30 ` [dpdk-dev] [PATCH v3 0/4] port: add ethdev_writer and ring_writer nodrop ports Dumitrescu, Cristian
2015-06-18 14:42   ` Thomas Monjalon [this message]

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=1455064.PMMjulFsjS@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=maciejx.t.gajdzica@intel.com \
    /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).