From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::22c]) by dpdk.org (Postfix) with ESMTP id E5DD02E8A for ; Wed, 30 Oct 2013 08:03:12 +0100 (CET) Received: by mail-lb0-f172.google.com with SMTP id c11so884820lbj.3 for ; Wed, 30 Oct 2013 00:04:04 -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=5UKa724vZmJOLrt6zLKDWIofW0ifmY/uD2UEBxEOzw8=; b=PgUeMzPcNJU8gpvWR0ICE6mPmIbPKiQ62JZ+7jktcUpKdYhg0c99uS8faClTXS6704 FwqBA7WmwdAsQGzxqpQwEcxhy3l7rcOq+nYchcifbC21ioYXESGT7vXUoAW+AzTdgvsX siBIvnh4Lt+qx2u43r8av6feCw9S0Fa7bivisbEIw/0xQuFIyp/lOdaH8Kw7hAgTNUF9 4uhPVi4R9ZX2zfAOwsgDvnOrZg4EZQjtSmseVWqDWZP3CgS8vDrINtVjcMbiLHjIc+BZ 0vS5t2+FQK6gXIDWGQJOXg+E1LN80tHSJaZYvtY5wMsfcztJXbmw9XFfJ3k7RgizGpdV kWRg== MIME-Version: 1.0 X-Received: by 10.152.5.69 with SMTP id q5mr299960laq.46.1383116643948; Wed, 30 Oct 2013 00:04:03 -0700 (PDT) Received: by 10.114.183.13 with HTTP; Wed, 30 Oct 2013 00:04:03 -0700 (PDT) In-Reply-To: References: Date: Wed, 30 Oct 2013 15:04:03 +0800 Message-ID: From: Jose Gavine Cueto To: Prashant Upadhyaya Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "dev@dpdk.org" 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 07:03:13 -0000 Hi Prashant, Are you referring to the rte_* libraries ? I had actually compiled them using the setup script ($(RTE_SDK)/tools/setup.sh) and then linked the PMD lib extension I've made and then linked the pktdump eventually, before seeing the problem. However, building it all as an app. didn't show any issue. I will try to redo the building/linking just to make sure. Thank you! On Wed, Oct 30, 2013 at 2:57 PM, Prashant Upadhyaya < prashant.upadhyaya@aricent.com> wrote: > Hi Pepe, > > How about this -- compile the libraries yourself and then link your > application with them just like the original usecase where you find the > problem. > If this works, then the problem is with the precompiled libraries you were > picking from somewhere. > > Regards > -Prashant > > > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jose Gavine Cueto > Sent: Wednesday, October 30, 2013 12:22 PM > To: dev@dpdk.org > Subject: Re: [dpdk-dev] rte_eth_rx_burst stops running on dpdk extlib > > 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. > > > > > > =============================================================================== > Please refer to http://www.aricent.com/legal/email_disclaimer.html > for important disclosures regarding this electronic communication. > > =============================================================================== > -- To stop learning is like to stop loving.