From: Olivier Deme <odeme@druidsoftware.com>
To: users@dpdk.org
Subject: [dpdk-users] rte_eth_tx_burst keeps returning 0 upon reaching TX throughput
Date: Tue, 20 Nov 2018 17:18:29 +0000 [thread overview]
Message-ID: <CAAfggZOwqfD4UkSrkg6APjPn4ZgNRERHAw_A7BmJ3moinUAkqQ@mail.gmail.com> (raw)
Hi,
I am currently experiencing an issue with our DPDK application
whereby rte_eth_tx_burst keeps returning 0 upon reaching a certain output
rate.
Our application is based on the run to completion model.
Packets are read in burst using rte_eth_rx_burst, processed and then sent
in burst by the same lcore using rte_eth_tx_burst.
An external application generates test traffic.
We are currently using only 1 lcore and trying to verify how much traffic
can be switched on that single core, before testing with multiple cores.
Everything appears to be working fine up to around 5Gbs of traffic.
But then, upon generating more traffic, we observe that rte_eth_tx_burst
starts failing consistently by returning 0 on every call.
We checked that the mempool has many free mbufs.
We also observed that when the problem occurs, a call to
rte_eth_link_get_nowait indicates that the link_speed has switched to 0
(while it wasn't 0 beforehand).
The only way to recover is to restart the application.
We are using a XL710 NIC within an LXC container.
Would anybody know what could cause this behaviour?
Many thanks.
reply other threads:[~2018-11-20 17:18 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=CAAfggZOwqfD4UkSrkg6APjPn4ZgNRERHAw_A7BmJ3moinUAkqQ@mail.gmail.com \
--to=odeme@druidsoftware.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).