From: Stephen Hemminger <stephen@networkplumber.org>
To: Scott Talbert <swt@techie.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] NIC Stops Transmitting
Date: Fri, 26 Jul 2013 12:53:22 -0700 [thread overview]
Message-ID: <20130726125322.0ecbca48@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <alpine.LRH.2.03.1307261538440.21740@techie.net>
On Fri, 26 Jul 2013 15:39:18 -0400 (EDT)
Scott Talbert <swt@techie.net> wrote:
> Hi,
>
> I'm writing an application using DPDK that transmits a large number of
> packets (it doesn't receive any). When I transmit at 2 Gb/sec, everything
> will run fine for several seconds (receiver is receiving at correct rate),
> but then the NIC appears to get 'stuck' and doesn't transmit any more
> packets. In this state, rte_eth_tx_burst() is returning zero (suggesting
> that there are no available transmit descriptors), but even if I sleep()
> for a second and try again, rte_eth_tx_burst() still returns 0. It almost
> appears as if a packet gets stuck in the transmit ring and keeps
> everything from flowing. I'm using an Intel 82599EB NIC.
>
> Does anyone have any ideas of what might be going on?
>
> Thanks,
> Scott
Make sure there is enough memory for mbufs.
Also what is your ring size and transmit free threshold?
It is easy to instrument the driver to see where it is saying "no space left"
Also be careful with threshold values, many values of pthresh/hthresh/wthresh
don't work. I would check the Intel reference manual for your hardware.
next prev parent reply other threads:[~2013-07-26 19:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 19:39 Scott Talbert
2013-07-26 19:53 ` Stephen Hemminger [this message]
2013-07-26 20:04 ` Scott Talbert
2013-07-26 22:31 ` jinho hwang
2013-07-26 23:26 ` Scott Talbert
2013-07-29 17:02 ` Scott Talbert
2013-07-31 2:43 ` [dpdk-dev] miss include file in DPDK 1.3.1r2 Jia.Sui
2013-07-31 9:18 ` [dpdk-dev] [PATCH] mem: fix include in rte_malloc Thomas Monjalon
2013-07-31 11:36 ` didier.pallard
2013-07-31 11:48 ` Thomas Monjalon
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=20130726125322.0ecbca48@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=swt@techie.net \
/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).