DPDK usage discussions
 help / color / mirror / Atom feed
From: Alex Kiselev <kiselev99@gmail.com>
To: users <users@dpdk.org>
Subject: [dpdk-users] tx error on bond port
Date: Fri, 7 Jul 2017 17:38:44 +0300	[thread overview]
Message-ID: <CAMKNYbxC1R7bioY97B+zMwnDgbr8NV0Fe=_GyyegcQXKhN3MZg@mail.gmail.com> (raw)

Hi!

I am using a bonding port build on top of two regular ports (X710-DA2 nic) and
I am facing sending errors. After some time of normal operations (~1
hour) without tx errors,
rte_eth_tx_burst function starts reporting that some packets have not been sent.
Tx packet rate is about 200-300 kilo packets per seconds. Restarting
my application
helps and tx errors disappear, but only for some time. Tx error rate
is about 200 errors
per second.

What could be a cause for those tx errors?
Is there some ways to debug and troubleshot that situation?

Thank you.

-- 
--
Alex Kiselev

                 reply	other threads:[~2017-07-07 14:38 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='CAMKNYbxC1R7bioY97B+zMwnDgbr8NV0Fe=_GyyegcQXKhN3MZg@mail.gmail.com' \
    --to=kiselev99@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).