From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qg0-f49.google.com (mail-qg0-f49.google.com [209.85.192.49]) by dpdk.org (Postfix) with ESMTP id 99619AFD1 for ; Wed, 28 May 2014 13:38:52 +0200 (CEST) Received: by mail-qg0-f49.google.com with SMTP id a108so17027013qge.22 for ; Wed, 28 May 2014 04:39:03 -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=hm29tvteG5321WVwg6EMNwI5FGaLlWdM7aqeexisnVA=; b=W8l7L6hx2Sdpwk0KTNwhK46BgQLF9sNcpCOwHkByXQIq+XOa7BmmGaOqDsDuQEwgx2 4AOXFw+JII3GzTFilqx3No8LWF7He59gfPRRmbZo3SgcLKnoyZijGWn5BMjFmuvmvEQt 65gMe9/tw1syjrMrc8BgH+FvUWD5t06nmjtuwpZYI1UnOys5l+agUlh7E7iuANhy/WH1 sT27jSgvwO/cCvu3IHG0VI4guN9uq0ddQv3mgVJHBil13+cdBigPASMK4WajrzzR/XqE AuYIFEjfGu/ETsJSzxBYG0H9DNbYLheG21VbSzM2e99p6sTk0Oq9I/c1SjM+xjmbkIzi NbcQ== MIME-Version: 1.0 X-Received: by 10.224.43.148 with SMTP id w20mr52661271qae.26.1401277143676; Wed, 28 May 2014 04:39:03 -0700 (PDT) Received: by 10.96.235.98 with HTTP; Wed, 28 May 2014 04:39:03 -0700 (PDT) In-Reply-To: <59AF69C657FD0841A61C55336867B5B01AA2F0A8@IRSMSX103.ger.corp.intel.com> References: <59AF69C657FD0841A61C55336867B5B01AA2F05B@IRSMSX103.ger.corp.intel.com> <59AF69C657FD0841A61C55336867B5B01AA2F0A8@IRSMSX103.ger.corp.intel.com> Date: Wed, 28 May 2014 17:09:03 +0530 Message-ID: From: sabu kurian To: "Richardson, Bruce" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 11:38:53 -0000 Hai bruce, I changed the burst size to 16. The code crafts 54 byte TCP packets. It sends a few packets and shows a segmentation fault. Below is the portion of the code that sends the packet. ret =3D rte_eth_tx_burst(1, 0, m_pool, burst_size); if (ret < 16) { for(i=3D(int)burst_size-ret;i<(int)burst_size;i++) { rte_pktmbuf_free(m_pool[i]); printf("\n Packet dropped %d",i); } } else { lcore_stats[lcore_id].tx +=3D (uint64_t)burst_size; } The above code is being run inside an infinite for loop. m_pool is an array (size 16) of mbuf's allocated using rte_pktmbuf_alloc. I'm trying to achieve maximum transfer rate. Is there any other way to do this with Intel DPDK or am I missing something ? The code works perfectly inside a virtual machine (VMWare) with emulated NIC's, but as expected the host kernel drops 99% of the packets. I'm using Intel=C2=AE Core=E2=84=A2 i7-3770 CPU @ 3.40GHz On Wed, May 28, 2014 at 4:48 PM, Richardson, Bruce < bruce.richardson@intel.com> wrote: > > > From: sabu kurian [mailto:sabu2kurian@gmail.com] > > Sent: Wednesday, May 28, 2014 11:54 AM > > To: Richardson, Bruce > > Cc: dev@dpdk.org > > Subject: Re: [dpdk-dev] Intel I350 fails to work with DPDK > > > > 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. > > Bursts of 64 and 128 are rather large, can you perhaps try using bursts o= f > 16 and 32 and see what the result is? The drivers are generally tuned for= a > max burst size of about 32 packets. > >