From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-la0-x235.google.com (mail-la0-x235.google.com [IPv6:2a00:1450:4010:c03::235]) by dpdk.org (Postfix) with ESMTP id 868FADE4 for ; Wed, 30 Oct 2013 07:51:31 +0100 (CET) Received: by mail-la0-f53.google.com with SMTP id eo20so706278lab.40 for ; Tue, 29 Oct 2013 23:52:22 -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 :content-type; bh=iowbR0jK3CnRwmk1u0uW1kQm9IDruWVA1v1IAXcIdbM=; b=DvmsnHAU6ybF41HUgszwhe45z1785P9Id8LSNa+J5kMlkbXBrhDGJk4QMLhfqO0Gef zpMOWpu81g9n+L1gI0Oc7ggRKjNf/dgldgWJpszHRUkjlsOGP1U7Gu/zXy463ou2QtzJ F3Yh5K6Ph37x64cvfaKn3ItKna/2e9+2J4WRg1sczDnfpTy97DNIHgYZhyPIYv+EJNpo hlW3r/1Zz16H2xbygcUuyqoOQH85zOtD4mdmaGk0feklPh7hYfHm9ogU2/KwHZ6gKcij qF6VmDiEFA34UzEZsl6pWzGht9ORKp7dULKh1VxBjvg2L3FFeYUETavCARBd3rssgDtm Yjrg== MIME-Version: 1.0 X-Received: by 10.152.170.133 with SMTP id am5mr476974lac.9.1383115942222; Tue, 29 Oct 2013 23:52:22 -0700 (PDT) Received: by 10.114.183.13 with HTTP; Tue, 29 Oct 2013 23:52:22 -0700 (PDT) In-Reply-To: References: Date: Wed, 30 Oct 2013 14:52:22 +0800 Message-ID: From: Jose Gavine Cueto To: dev@dpdk.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] rte_eth_rx_burst stops running on dpdk extlib 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, 30 Oct 2013 06:51:32 -0000 Hi, Could someone help me ? Or at least let me know if what I'm doing (diagram above) is right with regard to using a external dpdk library ? I assume dpdk external libraries can be treated as norma C libraries. Cheers, Pepe On Wed, Oct 30, 2013 at 8:18 AM, Jose Gavine Cueto wrote: > Hi, > > I'm writing a very simple packet dump application that can be described by > the following diagram: > > --------------------------- > | pktdump | > ---------------------------- > | PMD lib extension | > | (extlib) | > ---------------------------- > | DPDK PMD lib | > ---------------------------- > > pktdump - very simple app. built with gcc and linked with pmd lib > extension and dpdk libs. > pmd lib extension - an extension of dpdk pmd library, which provides some > higher-level APIs > dpdk pmd lib - pmd lib provided by Intel > > I have an issue where in when I run the pktdump app. it's lcore threads > stops executing at varying number of times. Sometimes it doesn't even run. > But this only happens if I use the PMD lib extension. On the other hand, > if pktdump is directly built with pmd lib extension code while pmd lib > extension is built as an extapp, it works very well. I wonder what's the > difference, code-wise there is none, the only difference I can see is how > they are built (extapp, extlib). > > The pmd lib extension's lcore threads basically do simple forwarding (rx > -> tx). So rte_eth_rx_burst is called when receiving packets and > rte_eth_tx_burst when transmitting packets. These runs on an lcore thread. > > snippet of code that runs on lcore: > > void burst_fwd(...){ > num_rx = rte_eth_rx_burst(...) > ... > rte_eth_tx_burst(...) > } > > Any tips on how to debug this, some quick inspections may help. Is there > some specific build options for building libraries, because this only > happens on extlib. > -- To stop learning is like to stop loving.