DPDK patches and discussions
 help / color / mirror / Atom feed
From: ran levi <ranlevi098@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Multi cores performance degradation
Date: Mon, 15 Dec 2014 06:56:42 +0200	[thread overview]
Message-ID: <CAEQdPQMy4zb72JtjW6uE8fyAr7ubisVafLtxFgjt8YdnE0UZUw@mail.gmail.com> (raw)

Hi,

I'm new to dpdk - played with execution_path, l2fwd and l3fwd examples.
I'm using 82599ES intel dual 10G interface on Xeon X5650 2.67GHz.

I got the following strange results with my tests:

1) Sending 10G in port 0 only - stand in line rate (no misses).
2) Sending 10G in port 1 only - stand in line rate.
3) Sending 20G (ports 0 and 1) and preform rte_eth_rx_burst() on both ports
with single lcore - stand in line rate .
4) Sending 20G (ports 0 and 1) and receiving each port in different lcore -
can't stand in line rate (rx misses).

I do not transmit the packets - just call rte_eth_rx_burst(), increase the
counters and free the mbuf.
All the lcores are on socket 0 (the one closer to the interface).

Any idea? How can i get line rate with multi cores?

Thanks,

Ran.

                 reply	other threads:[~2014-12-15  4:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAEQdPQMy4zb72JtjW6uE8fyAr7ubisVafLtxFgjt8YdnE0UZUw@mail.gmail.com \
    --to=ranlevi098@gmail.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).