From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qg0-f43.google.com (mail-qg0-f43.google.com [209.85.192.43]) by dpdk.org (Postfix) with ESMTP id 579F058DD for ; Wed, 28 May 2014 12:53:58 +0200 (CEST) Received: by mail-qg0-f43.google.com with SMTP id 63so17486508qgz.30 for ; Wed, 28 May 2014 03:54:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qiNtM8X+9vKZfvjZENPF6YnHw5YX5RS6dr1rIVnTARI=; b=dpziMAIYROxT7d9WQq23Gz43AUL5f9owoQHHSSz+V39/mrXLZ7DUuLE5wp2OF6mosy zQRhrvFR4k5GoG+z7/i2e1wrlKRS6cZ0wqZ4XCfbYqEMMxgDSEnmvHW9VCB/j/C5CnOK E2wlGiSCAM2+8AQJeJlONkC4da1uF6pFtA5I+0m/sODPuajNu/J7aE3eTtWhinkqj0UW 6b6At3le8jMQfQSNY6vvzUf4Q+97M7boJhwn3Gae2Q6QiFbP0kQo8kE/CbVzSmu2d3Bn CVaoxmIcfDr4bfuO9pCSJ6+x2hoSMu2u8bpp6/OLubXFBuuWO7dWhs+v+0TTBR1KtuJ9 2jog== MIME-Version: 1.0 X-Received: by 10.224.112.74 with SMTP id v10mr51218106qap.28.1401274449494; Wed, 28 May 2014 03:54:09 -0700 (PDT) Received: by 10.96.235.98 with HTTP; Wed, 28 May 2014 03:54:09 -0700 (PDT) In-Reply-To: <59AF69C657FD0841A61C55336867B5B01AA2F05B@IRSMSX103.ger.corp.intel.com> References: <59AF69C657FD0841A61C55336867B5B01AA2F05B@IRSMSX103.ger.corp.intel.com> Date: Wed, 28 May 2014 16:24:09 +0530 Message-ID: From: sabu kurian To: "Richardson, Bruce" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Intel I350 fails to work with DPDK X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 May 2014 10:53:58 -0000 Hai bruce, Thanks for the reply. I even tried that before. Having a burst size of 64 or 128 simply fails. The card would send out a few packets (some 400 packets of 74 byte size) and then freeze. For my application... I'm trying to generate the peak traffic possible with the link speed and the NIC. On Wed, May 28, 2014 at 4:16 PM, Richardson, Bruce < bruce.richardson@intel.com> wrote: > > -----Original Message----- > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of sabu kurian > > Sent: Wednesday, May 28, 2014 10:42 AM > > To: dev@dpdk.org > > Subject: [dpdk-dev] Intel I350 fails to work with DPDK > > > > I have asked a similar question before, no one replied though. > > > > I'm crafting my own packets in mbuf's (74 byte packets all) and sending > it > > using > > > > ret = rte_eth_tx_burst(port_ids[lcore_id], 0, m_pool,burst_size); > > > > When burst_size is 1, it does work. Work in the sense the NIC will > continue > > with sending packets, at a little over > > 50 percent of the link rate. For 1000 Mbps link rate .....The observed > > transmit rate of the NIC is 580 Mbps (using Intel DPDK). But it should be > > possible to achieve at least 900 Mbps transmit rate with Intel DPDK and > > I350 on 1 Gbps link. > > > > Could someone help me out on this ? > > > > Thanks and regards > > Sending out a single packet at a time is going to have a very high > overhead, as each call to tx_burst involves making PCI transactions (MMIO > writes to the hardware ring pointer). To reduce this penalty you should > look to send out the packets in bursts, thereby saving PCI bandwidth and > splitting the cost of each MMIO write over multiple packets. > > Regards, > /Bruce >