DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Gopakumar Choorakkot Edakkunni <gopakumar.c.e@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Performance of rte_ring APIs
Date: Mon, 10 Aug 2015 12:02:07 +0100	[thread overview]
Message-ID: <20150810110207.GA1100@bricha3-MOBL3> (raw)
In-Reply-To: <CABK1yFAun_-Sc0XvbL5Qini-5VR9eVBjD8eytK5COnKEYZ-1kw@mail.gmail.com>

On Fri, Aug 07, 2015 at 10:07:07AM -0700, Gopakumar Choorakkot Edakkunni wrote:
> Hi All,
> 
> I have an extremely simple test - I have just one single DPDK EAL
> thread which pulls packets from one 10G port and just puts the packet
> exactly as is (no changes) on another 10G port - I get 9.5million pps,
> so far so good. So its like this
> 
> dpdk_rx
> dpdk_tx
> 
> 9.5 Millionpps
> 
> Now I do the below and the performance comes down to like 4 Million
> pps, less than half !
> 
> dpdk_rx
> rte_ring_mc_dequeue_bulk(my_ring1, my_array, nb_rx)
> dpdk_tx
> rte_ring_mp_enqueue_bulk(my_ring1, my_array, nb_rx)
> 
> Note that I do nothing with the things I dequeue from the ring, I just
> enqueue it back. So is there any gotchas in using these rings ? I am
> sure I am missing something, it cant drop from 9.5Mpps to 4Mpps just
> because of a dequeue/enqueue ?
> 
You are using the multi-producer and multi-consumer ring functions, which tend to
be much more expensive than the single producer single consumer function. Depending
on the contention on those rings, performance can vary considerably in your application.

/Bruce

      reply	other threads:[~2015-08-10 11:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07 17:07 Gopakumar Choorakkot Edakkunni
2015-08-10 11:02 ` Bruce Richardson [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=20150810110207.GA1100@bricha3-MOBL3 \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=gopakumar.c.e@gmail.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).