DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Soni, Shivam" <shivsoni@amazon.com>
To: "dev@dpdk.org" <dev@dpdk.org>, "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-dev] TX unable to enqueue packets to NIC
Date: Tue, 8 Jan 2019 02:13:14 +0000	[thread overview]
Message-ID: <A5EB3F76-9340-4E5B-8365-95D806459ED2@amazon.com> (raw)
In-Reply-To: <166A645A-F5E1-44EC-A0E8-4C4B17AFF8DD@amazon.com>

Hi All,

We are facing one weird issue. After the deployment, in few of the hosts we see an issue where TX is unable to enqueue packets to NIC. On rebouncing or restarting our packet processor daemon, issue gets resolved.

We are using IntelDPDK version 17.11.4 and i40e drivers.

I have verified that all the interface initialization methods are not throwing any error during startup. Also tx_errors count in rte_eth_stats is 0.

We use dpdk_eth_tx_burst method to enqueue packets to NIC from TX which is returning 0. Verified this in testing environment where packets to be enqueued count is 1 but dpdk_eth_tx_burst  function is returning 0.
On wrapping this function call inside a while loop which checks for the number of enqueued packets to be equal to the count needs to be enqueued the app loops indefinitely.

Is there anything which is not getting reset during the deployment causing this issue to happen.

If someone has any idea on whats going on here please let me know. Any help is appreciated.

Thanks.
-Shivam

           reply	other threads:[~2019-01-08  2:13 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <166A645A-F5E1-44EC-A0E8-4C4B17AFF8DD@amazon.com>]

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=A5EB3F76-9340-4E5B-8365-95D806459ED2@amazon.com \
    --to=shivsoni@amazon.com \
    --cc=dev@dpdk.org \
    --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).