From: Jose Gavine Cueto <pepedocs@gmail.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] rte_eth_rx_burst stops running on dpdk extlib
Date: Wed, 30 Oct 2013 14:52:22 +0800 [thread overview]
Message-ID: <CAJ5bv6E2SMOtUnHixTbQk9P_iFTC3whujD3bq8HFv44AMxcC9A@mail.gmail.com> (raw)
In-Reply-To: <CAJ5bv6E1CL1e94yTjhZpyFgzDW9dThjJyiow1oCVp0VOvsLRYQ@mail.gmail.com>
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.
next prev parent reply other threads:[~2013-10-30 6:51 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 [this message]
2013-10-30 6:57 ` Prashant Upadhyaya
2013-10-30 7:04 ` Jose Gavine Cueto
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=CAJ5bv6E2SMOtUnHixTbQk9P_iFTC3whujD3bq8HFv44AMxcC9A@mail.gmail.com \
--to=pepedocs@gmail.com \
--cc=dev@dpdk.org \
/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).