From: Alexander Kiselev <kiselev99@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] TX descriptor is not done
Date: Sun, 16 Jul 2017 14:51:08 +0300 [thread overview]
Message-ID: <7683E5FD-3C6B-45A6-98E6-2C4ABC3497C8@gmail.com> (raw)
Hi.
Exсume me for bothering you here in the dev list. I was trying to get some help in the users list, but the only answer I got suggested to post here.
I am facing "TX descriptor is not done" problem that appears when I am using two i40e ports (x710-da2 nic) as slave ports of a bonding (lacp mode) port. Before I switched to using the bonding driver my application had been working for weeks without any problems. But now it works ok only for hours or days and then one of the tx queues stops transmitting packets. Last time tx queue number 2 (of total 5) failed on both slave ports at the same time.
What could cause that behavior?
Thank you.
--
Alex Kiselev
next reply other threads:[~2017-07-16 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-16 11:51 Alexander Kiselev [this message]
2017-07-20 11:30 ` Alex Kiselev
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=7683E5FD-3C6B-45A6-98E6-2C4ABC3497C8@gmail.com \
--to=kiselev99@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).