DPDK usage discussions
 help / color / mirror / Atom feed
From: Aswin Surendran <aswinsurendran93@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] No packets transmitted with rte_eth_tx_burst
Date: Tue, 28 Apr 2020 09:40:26 +0530	[thread overview]
Message-ID: <CAOoCAXZSojYE+TZYsrMfcGtCX8P=zukWKftCqabrurDGazqi0Q@mail.gmail.com> (raw)

Hi,

I face an issue when we use rte_eth_tx_burst on a VPP-DPDK application,
where none of the packets were transmitted out and the function returns 0.
Initially, packets were transmitted properly, but after a few hours, the
issue is seen.

The function rte_eth_tx_burst is called in the below API:
u32 tx_burst_vector_internal (vlib_main_t * vm, 191  dpdk_device_t * xd,
192  struct rte_mbuf **tx_vector)
Link:
https://docs.fd.io/vpp/17.07/de/d54/plugins_2dpdk_2device_2device_8c_source.html#l00190

I would like to know if there is an API available to check what exactly is
happening in the problematic case?
Please help to give some pointers for me to check.

Thanks in advance.

Regards,
Aswin

                 reply	other threads:[~2020-05-04 17:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAOoCAXZSojYE+TZYsrMfcGtCX8P=zukWKftCqabrurDGazqi0Q@mail.gmail.com' \
    --to=aswinsurendran93@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).