From mboxrd@z Thu Jan  1 00:00:00 1970
From: Scott Talbert <swt-HdGmbYkwPlSsTnJN9+BGXg@public.gmane.org>
Subject: Re: NIC Stops Transmitting
Date: Fri, 26 Jul 2013 19:26:59 -0400 (EDT)
Message-ID: <alpine.LRH.2.03.1307261924200.3700@techie.net>
References: <alpine.LRH.2.03.1307261538440.21740@techie.net>
 <20130726125322.0ecbca48@nehalam.linuxnetplumber.net>
 <alpine.LRH.2.03.1307261601190.21740@techie.net>
 <CAPQGAnHkqCHQ9g7OQXF5+w-nho78HdtgCh8YtXumnCz-jzNANg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: dev <dev-VfR2kkLFssw@public.gmane.org>
To: jinho hwang <hwang.jinho-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Return-path: <dev-bounces-VfR2kkLFssw@public.gmane.org>
In-Reply-To: <CAPQGAnHkqCHQ9g7OQXF5+w-nho78HdtgCh8YtXumnCz-jzNANg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request-VfR2kkLFssw@public.gmane.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev-VfR2kkLFssw@public.gmane.org>
List-Help: <mailto:dev-request-VfR2kkLFssw@public.gmane.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request-VfR2kkLFssw@public.gmane.org?subject=subscribe>
Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org
Sender: "dev" <dev-bounces-VfR2kkLFssw@public.gmane.org>

On Fri, 26 Jul 2013, jinho hwang wrote:

>> 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;
>>
> I am wondering whether you use multiple cores accessing the same
> receive queue. I had this problem before, but after I make the same
> number of receiving queues as the number of receiving cores, the
> problem disappeared. I did not dig more since I did not care how many
> receive queues I have did not matter.

Jinho,

Thanks.  I have only one queue (should I be using more?) but as far as I 
know, I'm only using one core to transmit as well.

Scott