From: Scott Talbert <swt@techie.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] NIC Stops Transmitting
Date: Fri, 26 Jul 2013 16:04:51 -0400 (EDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1307261601190.21740@techie.net> (raw)
In-Reply-To: <20130726125322.0ecbca48@nehalam.linuxnetplumber.net>
On Fri, 26 Jul 2013, Stephen Hemminger wrote:
>> 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.
>>
> 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.
Thanks for the tips. I don't think I'm running out of mbufs, but I'll
check that again. I am using these values from one of the examples -
which claim to be correct for the 82599EB.
/*
* These default values are optimized for use with the Intel(R) 82599 10
GbE
* Controller and the DPDK ixgbe PMD. Consider using other values for
other
* network controllers and/or network drivers.
*/
#define TX_PTHRESH 36 /**< Default values of TX prefetch threshold reg. */
#define TX_HTHRESH 0 /**< Default values of TX host threshold reg. */
#define TX_WTHRESH 0 /**< Default values of TX write-back threshold reg.
*/
static const struct rte_eth_txconf tx_conf = {
.tx_thresh = {
.pthresh = TX_PTHRESH,
.hthresh = TX_HTHRESH,
.wthresh = TX_WTHRESH,
},
.tx_free_thresh = 0, /* Use PMD default values */
.tx_rs_thresh = 0, /* Use PMD default values */
};
/*
* Configurable number of RX/TX ring descriptors
*/
#define RTE_TEST_TX_DESC_DEFAULT 512
static uint16_t nb_txd = RTE_TEST_TX_DESC_DEFAULT;
next prev parent reply other threads:[~2013-07-26 20:04 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
2013-07-26 20:04 ` Scott Talbert [this message]
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=alpine.LRH.2.03.1307261601190.21740@techie.net \
--to=swt@techie.net \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).