From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stephen@networkplumber.org>
Received: from mail-pd0-f174.google.com (mail-pd0-f174.google.com
 [209.85.192.174]) by dpdk.org (Postfix) with ESMTP id 62CB358EE
 for <dev@dpdk.org>; Fri, 26 Jul 2013 21:53:02 +0200 (CEST)
Received: by mail-pd0-f174.google.com with SMTP id 3so2232588pdj.19
 for <dev@dpdk.org>; Fri, 26 Jul 2013 12:53:25 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=google.com; s=20120113;
 h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer
 :mime-version:content-type:content-transfer-encoding
 :x-gm-message-state;
 bh=GevDZEtosopo6wknqi0fCao+KPbjLJP/XkHR2XniB1Q=;
 b=MG6ICySuKIo3KqBsz1cn8r1Cwt0z9Ek8wago8In560xGZuAxS7w5goPAu5CPmvRiLI
 FYY1qPnbKU8j3qW6RQvxtlV740BKXgdqmi8vvA2fi+G6AE06PKQ+/3TEwEclFgx+3o0J
 Dz36+r3FmZE9LBZEu4z/XG05k5uKPZVug27Fv6eZhyHBA71IzceP8nRL5fyg1/pgxRdZ
 zoN1l7gkTHaekShsKN0548zH9qWE1CJlk25ZvFenG9DCVLsTYInedOrq1R3/lMmkE5in
 N+JfWfYygAM17n6nocSzK0GKqL95nScx1GvYLKM2J84+VOY2v7CxDEDaL9duAstUvzlj
 Kq4g==
X-Received: by 10.66.13.233 with SMTP id k9mr10177599pac.57.1374868404944;
 Fri, 26 Jul 2013 12:53:24 -0700 (PDT)
Received: from nehalam.linuxnetplumber.net
 (static-50-53-71-109.bvtn.or.frontiernet.net. [50.53.71.109])
 by mx.google.com with ESMTPSA id iq3sm61746260pbb.20.2013.07.26.12.53.24
 for <multiple recipients>
 (version=TLSv1.2 cipher=RC4-SHA bits=128/128);
 Fri, 26 Jul 2013 12:53:24 -0700 (PDT)
Date: Fri, 26 Jul 2013 12:53:22 -0700
From: Stephen Hemminger <stephen@networkplumber.org>
To: Scott Talbert <swt@techie.net>
Message-ID: <20130726125322.0ecbca48@nehalam.linuxnetplumber.net>
In-Reply-To: <alpine.LRH.2.03.1307261538440.21740@techie.net>
References: <alpine.LRH.2.03.1307261538440.21740@techie.net>
X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQmaE24HfSCC1BZE6oveBjk2p+zUifk2Y9OMlFEL881sH+GT3tbB0LEVElB9ty6FeMb4qt3F
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] NIC Stops Transmitting
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jul 2013 19:53:02 -0000

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.