DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Michal Jastrzebski <michalx.k.jastrzebski@intel.com>,
	Maciej Gajdzica <maciejx.t.gajdzica@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 1/3] port: added WRITER_APPROACH == 1 implementation to ring port
Date: Sun, 17 May 2015 23:44:43 +0200	[thread overview]
Message-ID: <22373976.yBms5me9Vj@xps13> (raw)
In-Reply-To: <1430395084-6172-2-git-send-email-michalx.k.jastrzebski@intel.com>

2015-04-30 13:58, Michal Jastrzebski:
> From: Maciej Gajdzica <maciejx.t.gajdzica@intel.com>
> 
> Added better optimized implementation of tx_bulk for ring writer port
> based on
> similar solution in ethdev_writer port. New implementation sends burst
> without
> copying data to internal buffer if it is possible.
> 
> Signed-off-by: Maciej Gajdzica <maciejx.t.gajdzica@intel.com>
[...]
> +#if RTE_PORT_RING_WRITER_APPROACH == 0

Nack
Maybe you missed the previous comment:
	http://dpdk.org/ml/archives/dev/2015-March/015999.html

  reply	other threads:[~2015-05-17 21:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30 11:58 [dpdk-dev] [PATCH v2 0/3] port: added ethdev_writer_nodrop and ring_writer_nodrop ports Michal Jastrzebski
2015-04-30 11:58 ` [dpdk-dev] [PATCH v2 1/3] port: added WRITER_APPROACH == 1 implementation to ring port Michal Jastrzebski
2015-05-17 21:44   ` Thomas Monjalon [this message]
2015-05-19 22:49     ` Dumitrescu, Cristian
2015-05-19 23:19       ` Thomas Monjalon
2015-04-30 11:58 ` [dpdk-dev] [PATCH v2 2/3] port: added ethdev_writer_nodrop port Michal Jastrzebski
2015-04-30 11:58 ` [dpdk-dev] [PATCH v2 3/3] port: added ring_writer_nodrop port Michal Jastrzebski
2015-05-05 15:06 ` [dpdk-dev] [PATCH v2 0/3] port: added ethdev_writer_nodrop and ring_writer_nodrop ports Dumitrescu, Cristian

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=22373976.yBms5me9Vj@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=maciejx.t.gajdzica@intel.com \
    --cc=michalx.k.jastrzebski@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).