DPDK usage discussions
 help / color / mirror / Atom feed
* [dpdk-users] TX descriptor is not done, bonding driver LACP mode issues
@ 2017-07-14  8:23 Alex Kiselev
  0 siblings, 0 replies; only message in thread
From: Alex Kiselev @ 2017-07-14  8:23 UTC (permalink / raw)
  To: users, declan.doherty

Hi.

I will try to describe my problem shortly again so you don't need to
start reading the first posts in my thread "bonding driver LACP mode
issues".

I am having problems with bonding driver. The problems appeared right
after I switched from using two i40e ports to a single bonding port
build on top of the two i40e ports. Before changing the configuration
my application had been working for weeks without any problems.

I found out that after some time of normal operations tx queue 0 stop
transmitting with the error "TX descriptor is not done"

I google a little bit about "TX descriptor is not done" error and
found a discussion "NIC Stops Transmitting" where a guy was having the
same issues that I do.
http://dpdk.org/ml/archives/dev/2013-July/000357.html

One of the proposals to fix that problem was to check
pthresh/hthresh/wthresh values.

So, I start checking and found out that rte_eth_dev_info_get return 0
for for pthresh/hthresh/wthresh field, but recommended/default values
of this fields from i40e driver are completly different.

So far, it looks like this is what causing the bond port to stop
transmitting packets.

Is this a bug or a feature?

--
Alex Kiselev

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2017-07-14  8:23 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-07-14  8:23 [dpdk-users] TX descriptor is not done, bonding driver LACP mode issues Alex Kiselev

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).