From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <swt@techie.net>
Received: from bear.techie.net (bear.techie.net [205.134.185.202])
 by dpdk.org (Postfix) with ESMTP id 3DBB3559C
 for <dev@dpdk.org>; Mon, 29 Jul 2013 19:01:50 +0200 (CEST)
Received: from bear.techie.net (localhost.localdomain [127.0.0.1])
 by bear.techie.net (8.13.8/8.13.8) with ESMTP id r6TH2Epg024000
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
 Mon, 29 Jul 2013 13:02:14 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=techie.net; s=default;
 t=1375117334; bh=HU9g7l4zjDbQmDJRrE0FBMNlCmAFRmx4g/Edrh42Ba8=;
 h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:
 MIME-Version:Content-Type;
 b=iGwp2BkICsTpYUSihvVB3u/DOPXjB2AoF/Oa3IESos4V16Ghf7hQaFcZtClyW4V3a
 KyS3zmN6WPnIv62R7ko2dSV3FgOFNFQUFkrC5KM5dGpX5u2GdjmkiCJtTm/LLcA7Fi
 EE03V6A0lecGOtjnsqHw9vzuN3mZXkXobW+IKAno=
Received: from localhost (talbert@localhost)
 by bear.techie.net (8.13.8/8.13.8/Submit) with ESMTP id r6TH2EQT023997;
 Mon, 29 Jul 2013 13:02:14 -0400
X-Authentication-Warning: bear.techie.net: talbert owned process doing -bs
Date: Mon, 29 Jul 2013 13:02:14 -0400 (EDT)
From: Scott Talbert <swt@techie.net>
X-X-Sender: talbert@bear.techie.net
To: jinho hwang <hwang.jinho@gmail.com>
In-Reply-To: <alpine.LRH.2.03.1307261924200.3700@techie.net>
Message-ID: <alpine.LRH.2.03.1307291301430.23215@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>
 <alpine.LRH.2.03.1307261924200.3700@techie.net>
User-Agent: Alpine 2.03 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: dev <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: Mon, 29 Jul 2013 17:01:50 -0000

On Fri, 26 Jul 2013, Scott Talbert wrote:

>> 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.
>
> 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.

All,

It turns out that the problem appears to have been caused by me using a 
signal handler to control my data rates.  After switching to use RTE 
timers instead, I am able to transmit close to 10 Gb/sec reliably.

Thanks,
Scott