From: David Aldrich <david.aldrich.ntml@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] A question about l2fwd
Date: Wed, 24 Jun 2020 12:28:49 +0100 [thread overview]
Message-ID: <CAJK_ieh4dPQGgW2E_U4iGOGOYnK6wM+5bWWUscjSAhMddcNuvA@mail.gmail.com> (raw)
Hi,
I have a question about the l2fwd example, which concerns a basic question
about how dpdk works.
The main processing loop in l2fwd is *l2fwd_main_loop()* which calls
*rte_eth_rx_burst()* to retrieve packets from the rx_queue.
My question is: what processing loop is responsible for transferring
packets from the ethernet device to the rx_queue?
I ask this because we have written our own application based on l2fwd and
no packets are being returned by our app's call to
*rte_eth_rx_burst(). *However,
packets are returned in the case of l2fwd. I'm trying to identify the
difference between the non-working and working code.
Best regards
David
next reply other threads:[~2020-06-24 11:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 11:28 David Aldrich [this message]
2020-06-24 11:54 ` Van Haaren, Harry
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=CAJK_ieh4dPQGgW2E_U4iGOGOYnK6wM+5bWWUscjSAhMddcNuvA@mail.gmail.com \
--to=david.aldrich.ntml@gmail.com \
--cc=users@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).