From: Jose Gavine Cueto <pepedocs@gmail.com>
To: Prashant Upadhyaya <prashant.upadhyaya@aricent.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] rte_eth_rx_burst stops running on dpdk extlib
Date: Wed, 30 Oct 2013 15:04:03 +0800 [thread overview]
Message-ID: <CAJ5bv6GDMeooghsou8XtCustF-SrDgKC0g=he0s2FBOmcoxWow@mail.gmail.com> (raw)
In-Reply-To: <C7CE7EEF248E2B48BBA63D0ABEEE700C45DF9E38FF@GUREXMB01.ASIAN.AD.ARICENT.COM>
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 <pepedocs@gmail.com
> >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.
next prev parent reply other threads:[~2013-10-30 7:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 0:18 Jose Gavine Cueto
2013-10-30 6:52 ` Jose Gavine Cueto
2013-10-30 6:57 ` Prashant Upadhyaya
2013-10-30 7:04 ` Jose Gavine Cueto [this message]
2013-10-30 7:13 ` Prashant Upadhyaya
2013-10-30 7:18 ` Jose Gavine Cueto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ5bv6GDMeooghsou8XtCustF-SrDgKC0g=he0s2FBOmcoxWow@mail.gmail.com' \
--to=pepedocs@gmail.com \
--cc=dev@dpdk.org \
--cc=prashant.upadhyaya@aricent.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).