From: David Marchand <david.marchand@6wind.com>
To: Maciej Gajdzica <maciejx.t.gajdzica@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/3] port: added WRITER_APPROACH == 1 implementation to ring port
Date: Mon, 30 Mar 2015 22:50:36 +0200 [thread overview]
Message-ID: <CALwxeUuzbiJsNZsUsfB1+vQpSkGmhdukUU_o6LMGX1hV8BwHeg@mail.gmail.com> (raw)
In-Reply-To: <1427709404-28921-2-git-send-email-maciejx.t.gajdzica@intel.com>
On Mon, Mar 30, 2015 at 11:56 AM, Maciej Gajdzica <
maciejx.t.gajdzica@intel.com> wrote:
> 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.
>
Well, if this is such a better implementation, then remove the old one.
We don't want dead code.
>
> ---
> lib/librte_port/rte_port_ring.c | 59
> +++++++++++++++++++++++++++++++++++++++
> 1 file changed, 59 insertions(+)
>
> diff --git a/lib/librte_port/rte_port_ring.c
> b/lib/librte_port/rte_port_ring.c
> index fa3d77b..ba2eeb3 100644
> --- a/lib/librte_port/rte_port_ring.c
> +++ b/lib/librte_port/rte_port_ring.c
> @@ -96,11 +96,14 @@ rte_port_ring_reader_free(void *port)
> /*
> * Port RING Writer
> */
> +#define RTE_PORT_RING_WRITER_APPROACH 1
> +
>
Seriously, can't we just drop this ?
Having build options everywhere is a pain.
Having this kind of stuff is worse ...
I can see other places that do the same, are these parts maintained ?
--
David Marchand
next prev parent reply other threads:[~2015-03-30 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 9:56 [dpdk-dev] [PATCH 0/3] port: added ethdev_writer_nodrop and ring_writer_nodrop ports Maciej Gajdzica
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 [this message]
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
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=CALwxeUuzbiJsNZsUsfB1+vQpSkGmhdukUU_o6LMGX1hV8BwHeg@mail.gmail.com \
--to=david.marchand@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).