DPDK patches and discussions
 help / color / mirror / Atom feed
From: Scott Talbert <swt@techie.net>
To: jinho hwang <hwang.jinho@gmail.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] NIC Stops Transmitting
Date: Fri, 26 Jul 2013 19:26:59 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LRH.2.03.1307261924200.3700@techie.net> (raw)
In-Reply-To: <CAPQGAnHkqCHQ9g7OQXF5+w-nho78HdtgCh8YtXumnCz-jzNANg@mail.gmail.com>

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

  reply	other threads:[~2013-07-26 23:26 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
2013-07-26 22:31     ` jinho hwang
2013-07-26 23:26       ` Scott Talbert [this message]
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.1307261924200.3700@techie.net \
    --to=swt@techie.net \
    --cc=dev@dpdk.org \
    --cc=hwang.jinho@gmail.com \
    /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).