DPDK usage discussions
 help / color / mirror / Atom feed
From: MESSI SHIYEH <shiyehgo@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] 1518B of 1G NIC can't achieve 100% throughput
Date: Wed, 12 Oct 2016 16:20:28 +0800	[thread overview]
Message-ID: <CAEr21XvXpVXrYfNdz-VHDkNRM4cjM62Wq8+3J4dne2KY9uWJoA@mail.gmail.com> (raw)

Hi all,

I have a bay trail platform as shown below:
 ===============================================
||  Atom N2807 --> PCIE Switch --> Intel I210 --> RJ45 Eth1    ||
||                                                     |
                                   ||
||                                                     | --> Intel I210 -->
RJ45 Eth2    ||
 ===============================================

Now I run RFC2544 throughput test for Linux native ip forwarding,
and get the result as show below:
================================
||  Frame Size(bytes)  ||  Throughput(%)  ||
||                         1518   ||  100                      ||
================================
Focus on 1518B, the throughput is totally 100%.

However, I run RFC2544 test with DPDK (testpmd),
and here is the result.
================================
||  Frame Size(bytes)  ||  Throughput(%)   ||
||                        1518    ||  99.297                 ||
================================
(My command is: #./testpmd -c 0x3 -n 1 -- -i --nb-cores=1 --nb-ports=2
--total-num-mbufs=2048)
The throughput of 1518B is just only 99.297%,
which means it is failed when running 100% offered loading because there is
a few frame loss (~0.5%).

Could anyone help us to explain the phenomenon?
Could anyone help us to improve it to 100%?

BTW, I just attempted to modify these parameters like rxd, txd, txwt,
burst, etc,..
but it doesn't seem work to me.

PS.

OS: CentOS 7.1 x64

Kernel: 3.10.0-229

DPDK ver: 16.04


BR,

Leo,

                 reply	other threads:[~2016-10-12  8:21 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=CAEr21XvXpVXrYfNdz-VHDkNRM4cjM62Wq8+3J4dne2KY9uWJoA@mail.gmail.com \
    --to=shiyehgo@gmail.com \
    --cc=users@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).