From: "Wu, Yiwen" <yiwen.wu76@gmail.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: No egressing packet
Date: Wed, 16 Sep 2015 09:30:34 -0400 [thread overview]
Message-ID: <55F96EFA.8050006@gmail.com> (raw)
In-Reply-To: <1944265.eVANXui8GP@xps13>
Thomas,
I am using rte_eth_tx_burst to send packets. I also use
rte_eth_add_tx_callback to register a callback to figure out what has
been sent.
Thanks,
Yiwen
On 9/16/2015 3:32 AM, Thomas Monjalon wrote:
> 2015-09-15 17:10, Wu, Yiwen:
>> Hi all,
>>
>> I am new to dpdk. I am running a single forwarding program based on dpdk
>> 2.1.0. The program runs on a VM, binding on two interfaces. All it's
>> doing is to forward packets from one interface to another. All
>> ingressing packets are fine but there seems no egressing packets. I used
>> rte_eth_add_tx_callback to register a tx callback. The callback is able
>> to print the right egress packet but the destination is just not
>> receiving it (via tcpdump). Does anybody have the similar experience?
>> Any solution or hints will be great.
> You need to call rte_eth_tx_burst() instead of rte_eth_add_tx_callback().
> For more information, please check the guide:
> http://dpdk.org/doc/guides/prog_guide/poll_mode_drv.html#poll-mode-driver
> You can also check this basic example:
> http://dpdk.org/browse/dpdk/tree/examples/skeleton/basicfwd.c
next prev parent reply other threads:[~2015-09-16 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 21:10 No egressing packet Wu, Yiwen
2015-09-16 7:32 ` Thomas Monjalon
2015-09-16 13:30 ` Wu, Yiwen [this message]
2015-09-16 13:35 ` Richardson, Bruce
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=55F96EFA.8050006@gmail.com \
--to=yiwen.wu76@gmail.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.