DPDK usage discussions
 help / color / mirror / Atom feed
From: DESBRUS Maxime <maxime.desbrus@thalesgroup.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Small constant frame loss only for more than 5 seconds of traffic at 10Gbps
Date: Tue, 12 Sep 2017 17:40:48 +0200	[thread overview]
Message-ID: <6C26BDBD2FD19B418E20F4A951DDC74A1A09061FCA@THSONEA01CMS08P.one.grp> (raw)

Hello

I am trying to capture 60 B Ethernet frames at link speed on two 10GbE ports with DPDK 17.08 on Linux 4.4 and an Intel XL710 card.

I use a slightly modified version of the l2fwd example program, that only counts incoming frames and immediately releases the mbufs.

I see a strange behavior because I can capture without any loss for 5s of traffic, but for more than that I always lose a few frames (about 15 000). For 10, 30 or 60 seconds of traffic the number of lost frames does not change much (it is a constant, and not a percentage of the incoming traffic).

I did apply all the recommendations to eliminate perturbations on the working cores:
* isolate cores with isolcpus, nohz_full, rcu_nocbs boot parameters
* disable hyper threading
* disable NMI watchdog
* disable pstate frequency scaling
* disable pause frames on both sides

I also tried to tweak a few things:
* increase/decrease mbuf pool size
* use a dedicated rte_mempool object per port
* increase/decrease packet burst length
* increase/decrease rx descriptor count

Although some of these did decrease loss a bit, I still get a few thousands lost frames for more than 5 seconds of incoming traffic.

I don't understand why performance seem to change only after a few seconds of traffic.

Any ideas?

Thanks

--
Maxime DESBRUS

                 reply	other threads:[~2017-09-12 15:40 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=6C26BDBD2FD19B418E20F4A951DDC74A1A09061FCA@THSONEA01CMS08P.one.grp \
    --to=maxime.desbrus@thalesgroup.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).